"text":"UnidataAWIPSUserManual\n\uf0c1\n\n\n\n\nUnidataAWIPS\nisameteorologicaldisplayandanalysispackageoriginallydevelopedbythe\nNationalWeatherService\nand\nRaytheon\n,repackagedbyUnidatatosupportnon-operationaluseinresearchandeducationby\nUCARmemberinstitutions\n.\n\n\nAWIPStakesaunifiedapproachtodataingest,andmostdatatypesfollowapaththroughthesystemstartingwithan\nLDM\nclientrequestingdatafromthe\nUnidataIDD\n.ThesedatafilesarethendecodedandstoredasHDF5andPostgresmetadataby\nEDEX\n.\n\n\nUnidatasupportstwovisualizationframeworksforrenderingdata:\nCAVE\n,andthePythonDataAccessFramework(\npython-awips\n).\n\n\n\n\nInstallCAVE17.1.1\n\uf0c1\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nLinuxx86_64\n\n\ninstallCAVE.sh\n\n\n\n\n\n\nmacOS\n\n\nDownloadandinstallboth\nawips2-cave-17.1.1.dmg\nawips-python.pkg\n\n\n\n\n\n\n32-bitWindows\n\n\nawips-cave.msi\n\n\n\n\n\n\n64-bitWindows\n\n\nawips-cave.amd64.msi\n\n\n\n\n\n\n\n\n\n\nEDEXDataServer17.1.1\n\uf0c1\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nLinuxx86_64\n\n\ninstallEDEX.sh\n\n\n\n\n\n\n\n\nReadfullEDEXinstallinstructions...\n\n\n\n\nLicense\n\uf0c1\n\n\nUnidataAWIPSsourcecodeandbinaries(RPMs)areconsideredtobeinthepublicdomain,meaningtherearenorestrictionsonanydownload,modification,ordistributioninanyform(originalormodified).UnidataAWIPScontainsnoproprieterycontentandisthereforenotsubjecttoexportcontrolsasstatedinthe\nMasterRights\nlicensingfile.\n\n\n\n\n\n\nSoftwareComponents\n\uf0c1\n\n\n\n\nEDEX\n\n\nCAVE\n\n\nLDM\n\n\nedexBridge\n\n\nQpid\n\n\nPostgreSQL\n\n\nHDF5\n\n\nPyPIES\n\n\n\n\nTheprimaryAWIPSapplicationfordataingest,processing,andstorageistheEnvironmentalDataEXchange(\nEDEX\n)server;theprimaryAWIPSapplicationforvisualization/datamanipulationistheCommonAWIPSVisualizationEnvironment(\nCAVE\n)client,whichistypicallyinstalledonaworkstationseparatefromotherAWIPScomponents.\n\n\nInadditiontoprogramsdevelopedspecificallyforAWIPS,AWIPSusesseveralcommercialoff-the-shelf(COTS)andFreeorOpenSourcesoftware(FOSS)productstoassistinitsoperation.Thefollowingcomponents,workingtogetherandcommunicating,composetheentireAWIPSsystem.\n\n\nEDEX\n\uf0c1\n\n\nThemainserverforAWIPS.QpidsendsalertstoEDEXwhendatastoredbytheLDMisreadyforprocessing.TheseQpidmessagesincludefileheaderinformationwhichallowsEDEXtodeterminetheappropriatedatadecodertouse.Thedefaultingestserver(simplynamedingest)handlesalldataingestotherthangribmessages,whichareprocessedbyaseparateingestGribserver.Afterdecoding,EDEXwritesmetadatatothedatabaseviaPostgresandsavestheprocesseddatainHDF5viaPyPIES.AthirdEDEXserver,request,feedsrequesteddatatoCAVEclients.EDEXingestandrequestserversarestartedandstoppedwiththecommands\nedexstart\nand\nedexstop\n,whichrunsthesystemscript\n/etc/rc.d/init.d/edex_camel\n\n\n\n\nReadMore:HowtoInstallEDEX\n\n\n\n\nCAVE\n\uf0c1\n\n\nCommonAWIPSVisualizationEnvironment.ThedatarenderingandvisualizationtoolforAWIPS.CAVEcontainsofanumberofdifferentdatadisplayconfigurationscalledperspectives.Perspectivesusedinoperationalforecastingenvironmentsinclude\nD2D\n(DisplayTwo-Dimensional),\nGFE\n(GraphicalForecastEditor),and\nNCP\n(NationalCentersPerspective).CAVEisstartedwiththecommand\n/awips2/cave/cave.sh\nor\ncave.sh\n\n\n\n\nReadMore:HowtoInstallCAVE\n\n\n\n\n\n\nLDM\n\uf0c1\n\n\nhttp://www.unidata.ucar.edu/software/ldm/\n\n\nThe \nLDM\n (Local Data Manager), developed and supported by Unidata, is a suite of client and server programs designed for data distribution, and is the fundamental component comprising the Unidata Internet Data Distribution (IDD) system. In AWIPS, the LDM provides data feeds for grids, surface observations, upper-air profiles, satellite and r
"text":"Unidata AWIPS is a meteorological display and analysis package originally developed by the National Weather Service and Raytheon , repackaged by Unidata to support non-operational use in research and education by UCAR member institutions . AWIPS takes a unified approach to data ingest, and most data types follow a path through the system starting with an LDM client requesting data from the Unidata IDD . These data files are then decoded and stored as HDF5 and Postgres metadata by EDEX . Unidata supports two visualization frameworks for rendering data: CAVE , and the Python Data Access Framework ( python-awips ).",
"text":"Linux x86_64 installCAVE.sh macOS Download and install both awips2-cave-17.1.1.dmg awips-python.pkg 32-bit Windows awips-cave.msi 64-bit Windows awips-cave.amd64.msi",
"text":"Unidata AWIPS source code and binaries (RPMs) are considered to be in the public domain, meaning there are no restrictions on any download, modification, or distribution in any form (original or modified). Unidata AWIPS contains no proprietery content and is therefore not subject to export controls as stated in the Master Rights licensing file.",
"title":"License"
},
{
"location":"/#software-components",
"text":"EDEX CAVE LDM edexBridge Qpid PostgreSQL HDF5 PyPIES The primary AWIPS application for data ingest, processing, and storage is the Environmental Data EXchange ( EDEX ) server; the primary AWIPS application for visualization/data manipulation is the Common AWIPS Visualization Environment ( CAVE ) client, which is typically installed on a workstation separate from other AWIPS components. In addition to programs developed specifically for AWIPS, AWIPS uses several commercial off-the-shelf (COTS) and Free or Open Source software (FOSS) products to assist in its operation. The following components, working together and communicating, compose the entire AWIPS system.",
"title":"Software Components"
},
{
"location":"/#edex",
"text":"The main server for AWIPS. Qpid sends alerts to EDEX when data stored by the LDM is ready for processing. These Qpid messages include file header information which allows EDEX to determine the appropriate data decoder to use. The default ingest server (simply named ingest) handles all data ingest other than grib messages, which are processed by a separate ingestGrib server. After decoding, EDEX writes metadata to the database via Postgres and saves the processed data in HDF5 via PyPIES. A third EDEX server, request, feeds requested data to CAVE clients. EDEX ingest and request servers are started and stopped with the commands edex start and edex stop , which runs the system script /etc/rc.d/init.d/edex_camel Read More: How to Install EDEX",
"title":"EDEX"
},
{
"location":"/#cave",
"text":"Common AWIPS Visualization Environment. The data rendering and visualization tool for AWIPS. CAVE contains of a number of different data display configurations called perspectives. Perspectives used in operational forecasting environments include D2D (Display Two-Dimensional), GFE (Graphical Forecast Editor), and NCP (National Centers Perspective). CAVE is started with the command /awips2/cave/cave.sh or cave.sh Read More: How to Install CAVE",
"title":"CAVE"
},
{
"location":"/#ldm",
"text":"http://www.unidata.ucar.edu/software/ldm/ The LDM (Local Data Manager), developed and supported by Unidata, is a suite of client and server programs designed for data distribution, and is the fundamental component comprising the Unidata Internet Data Distribution (IDD) system. In AWIPS, the LDM provides data feeds for grids, surface observations, upper-air profiles, satellite and radar imagery and various other meteorological datasets. The LDM writes data directly to file and alerts EDEX via Qpid when a file is available for processing. The LDM is started and stopped with the commands edex start and edex stop , which runs the commands service edex_ldm start and service edex_ldm stop",
"title":"LDM"
},
{
"location":"/#edexbridge",
"text":"edexBridge, invoked in the LDM configuration file /awips2/ldm/etc/ldmd.conf , is used by the LDM to post \"data available\" messaged to Qpid, which alerts the EDEX Ingest server that a file is ready for processing.",
"title":"edexBridge"
},
{
"location":"/#qpid",
"text":"http://qpid.apache.org Apache Qpid , the Queue Processor Interface Daemon, is the messaging system used by AWIPS to facilitate communication between services. When the LDM receives a data file to be processed, it employs edexBridge to send EDEX ingest servers a message via Qpid. When EDEX has finished decoding the file, it sends CAVE a message via Qpid that data are available for display or further processing. Qpid is started and stopped by edex start and edex stop , and is controlled by the system script /etc/rc.d/init.d/qpidd",
"title":"Qpid"
},
{
"location":"/#postgresql",
"text":"http://www.postgresql.org PostgreSQL , known simply as Postgres, is a relational database management system (DBMS) which handles the storage and retrieval of metadata, database tables and some decoded data. The storage and reading of EDEX metadata is handled by the Postgres DBMS. Users may query the metadata tables by using the termainal-based front-end for Postgres called psql . Postgres is started and stopped by edex start and edex stop , and is controlled by the system script /etc/rc.d/init.d/edex_postgres",
"title":"PostgreSQL"
},
{
"location":"/#hdf5",
"text":"http://www.hdfgroup.org/HDF5/ Hierarchical Data Format (v.5) is the primary data storage format used by AWIPS for processed grids, satellite and radar imagery and other products. Similar to netCDF, developed and supported by Unidata, HDF5 supports multiple types of data within a single file. For example, a single HDF5 file of radar data may contain multiple volume scans of base reflectivity and base velocity as well as derived products such as composite reflectivity. The file may also contain data from multiple radars. HDF5 is stored in /awips2/edex/data/hdf5/",
"title":"HDF5"
},
{
"location":"/#pypies-httpd-pypies",
"text":"PyPIES , Python Process Isolated Enhanced Storage, was created for AWIPS to isolate the management of HDF5 Processed Data Storage from the EDEX processes. PyPIES manages access, i.e., reads and writes, of data in the HDF5 files. In a sense, PyPIES provides functionality similar to a DBMS (i.e PostgreSQL for metadata); all data being written to an HDF5 file is sent to PyPIES, and requests for data stored in HDF5 are processed by PyPIES. PyPIES is implemented in two parts: 1. The PyPIES manager is a Python application that runs as part of an Apache HTTP server, and handles requests to store and retrieve data. 2. The PyPIES logger is a Python process that coordinates logging. PyPIES is started and stopped by edex start and edex stop , and is controlled by the system script /etc/rc.d/init.d/https-pypies",
"text":"Download and Install CAVE\n\uf0c1\n\n\n\n\n\n\n\n\n\n\n\n\n\n\ncurrent release 17.1.1\n\n\n\n\n\n\n\n\n\n\nLinux x86_64\n\n\ninstallCAVE.sh \n\n\n\n\n\n\nmacOS\n\n\nDownload and install both\nawips2-cave-17.1.1.dmg \nawips-python.pkg \n\n\n\n\n\n\n32-bit Windows\n\n\nawips-cave.msi \n\n\n\n\n\n\n64-bit Windows\n\n\nawips-cave.amd64.msi \n\n\n\n\n\n\n\n\n\n\n Linux\n\uf0c1\n\n\n\n\ninstallCAVE.sh \n\n\n\n\nFor CentOS/Red Hat 6 and 7. Installs to \n/awips2/cave\n and writes files to \n~/caveData\n.\n\n\nInstall as root (all package dependencies should be resolved by yum)\n\n\nchmod 755 ./installCAVE.sh\n./installCAVE.sh\n\n\n\nRun CAVE from the menu \nApplications\n \n \nInternet\n \n \nAWIPS CAVE\n, or from the command line as simply \ncave\n.\n\n\n\n\n\n\nSystem Requirements\n\n\n\n\nx86_64 CentOS/RHEL 6 or 7\n\n\nOpenGL 2.0\n\n\n4GB RAM\n\n\nLatest NVIDIA driver\n for your graphics card\n\n\n2GB disk space for caching datasets in \n~/caveData\n\n\n\n\n\n\n\n\n macOS\n\uf0c1\n\n\nCAVE for macOS requires the \nawips-python.pkg\n package be installed in order for \nderived parameters\n to work.\n\n\n\n\nawips2-cave-17.1.1.dmg \n\n\nawips-python.pkg \n\n\n\n\nawips-python.pkg\n is not a prerequisite, and CAVE will still run and display data without it, but to use any derived parameter functions such as wind barbs/arrows and grid parameters on various vertical coordinates, \njep\n must be installed in some way (it is assumed in \n/Library/Python/2.7/site-packages/jep/\n). You are free to install jep yourself but should know that simply to install via source code or pip requires the Oracle JDK and Xcode and its Command Line Tools. The \nawips-python.pkg\n package is provided as a workaround for this.\n\n\n\n\nCAVE for macOS writes and syncs files to ~/Library/caveData\n\n\n\n\n\n\n Windows\n\uf0c1\n\n\nWindows clients are still based on the CAVE 16.2.2 code base and provided in lieu of no 17.1.1 client.\n\n\n\n\nawips-cave.msi \n\n\nawips-cave.amd64.msi \n\n\n\n\nWrites files to \ncaveData\n in the user's home directory.\n\n\n\n\nBeta status\n\n\nClient-side Python scripts (including Derived Parameters) do not work on Windows\n\n\n\n\n\n\nAWIPS Data in the Cloud\n\uf0c1\n\n\nUnidata and XSEDE Jetstream have partnered to offer a EDEX data server in the cloud, open to the Unidata university community. Select the server in the Connectivity Preferences dialog, or enter \nedex-cloud.unidata.ucar.edu\n (without \nhttp://\n before, or \n:9581/services\n after).\n\n\n\n\n\n\nTroubleshooting\n\uf0c1\n\n\nLocalization Preferences Error\n\n\nYou can reset CAVE by removing the \n~/caveData\n directory (on macOS \n~/Library/caveData\n) and then run \ncave\n again to connect to an EDEX server. Your local files have been removed, but if you are re-connecting to an EDEX server you have used before, the remote files will sync again to your local \n~/caveData\n (bundles, colormaps, etc.).\n\n\nNo Images Displayed\n\n\nIf you are able to load wire-frame contours but not images, \nupdate your video driver\n.",
"text":"current release 17.1.1 Linux x86_64 installCAVE.sh macOS Download and install both awips2-cave-17.1.1.dmg awips-python.pkg 32-bit Windows awips-cave.msi 64-bit Windows awips-cave.amd64.msi",
"text":"installCAVE.sh For CentOS/Red Hat 6 and 7. Installs to /awips2/cave and writes files to ~/caveData . Install as root (all package dependencies should be resolved by yum) chmod 755 ./installCAVE.sh\n./installCAVE.sh Run CAVE from the menu Applications Internet AWIPS CAVE , or from the command line as simply cave . System Requirements x86_64 CentOS/RHEL 6 or 7 OpenGL 2.0 4GB RAM Latest NVIDIA driver for your graphics card 2GB disk space for caching datasets in ~/caveData",
"text":"CAVE for macOS requires the awips-python.pkg package be installed in order for derived parameters to work. awips2-cave-17.1.1.dmg awips-python.pkg awips-python.pkg is not a prerequisite, and CAVE will still run and display data without it, but to use any derived parameter functions such as wind barbs/arrows and grid parameters on various vertical coordinates, jep must be installed in some way (it is assumed in /Library/Python/2.7/site-packages/jep/ ). You are free to install jep yourself but should know that simply to install via source code or pip requires the Oracle JDK and Xcode and its Command Line Tools. The awips-python.pkg package is provided as a workaround for this. CAVE for macOS writes and syncs files to ~/Library/caveData",
"text":"Windows clients are still based on the CAVE 16.2.2 code base and provided in lieu of no 17.1.1 client. awips-cave.msi awips-cave.amd64.msi Writes files to caveData in the user's home directory. Beta status Client-side Python scripts (including Derived Parameters) do not work on Windows",
"text":"Unidata and XSEDE Jetstream have partnered to offer a EDEX data server in the cloud, open to the Unidata university community. Select the server in the Connectivity Preferences dialog, or enter edex-cloud.unidata.ucar.edu (without http:// before, or :9581/services after).",
"text":"Localization Preferences Error You can reset CAVE by removing the ~/caveData directory (on macOS ~/Library/caveData ) and then run cave again to connect to an EDEX server. Your local files have been removed, but if you are re-connecting to an EDEX server you have used before, the remote files will sync again to your local ~/caveData (bundles, colormaps, etc.). No Images Displayed If you are able to load wire-frame contours but not images, update your video driver .",
"text":"installEDEX.sh Installs to subdirectories in /awips2 System Requirements 64-bit CentOS/RHEL 6 or 7 8 CPU cores (16 recommended) 16GB RAM (32+GB recommended for full IDD processing) 500GB disk space, more if you build a data archive. An SSD is an especially good idea , mounted to /awips2/edex/data/hdf5 to contain the decoded data files, or mounted to /awips2 to contain the entire AWIPS software system. EDEX can scale to any system , either by adjusting the incoming data feeds, or the resources allocated to each data type, but when selecting a server, more is always better . 64-bit CentOS/RHEL 6 and 7 are the only supported Linux operating systems. You may have luck with Fedora Core 12 to 14 and Scientific Linux. EDEX is not developed, tested, or supported on Debian, Ubuntu, SUSE, Solaris, OS X, or Windows.",
"text":"Create user and group awips:fxalpha groupadd fxalpha useradd -G fxalpha awips or if the awips account already exists: groupadd fxalpha usermod -G fxalpha awips",
"title":"Users and Groups"
},
{
"location":"/install/install-edex/#iptables",
"text":"Configure iptables to allow TCP connections on ports 5672, 9581 and 9582 To open ports to all connections vi /etc/sysconfig/iptables\n\n*filter\n:INPUT ACCEPT [0:0]\n:FORWARD ACCEPT [0:0]\n:OUTPUT ACCEPT [0:0]\n-A INPUT -m state --state ESTABLISHED,RELATED -j ACCEPT\n-A INPUT -p icmp -j ACCEPT\n-A INPUT -i lo -j ACCEPT\n-A INPUT -m state --state NEW -m tcp -p tcp --dport 22 -j ACCEPT\n-A INPUT -m state --state NEW -m tcp -p tcp --dport 5672 -j ACCEPT\n-A INPUT -m state --state NEW -m tcp -p tcp --dport 9581 -j ACCEPT\n-A INPUT -m state --state NEW -m tcp -p tcp --dport 9582 -j ACCEPT\n-A INPUT -j REJECT --reject-with icmp-host-prohibited\n-A FORWARD -j REJECT --reject-with icmp-host-prohibited\nCOMMIT To open ports to specific IP addresses vi /etc/sysconfig/iptables\n\n*filter\n:INPUT DROP [0:0]\n:FORWARD DROP [0:0]\n:OUTPUT ACCEPT [0:0]\n:EXTERNAL - [0:0]\n:EDEX - [0:0]\n-A INPUT -i lo -j ACCEPT\n-A INPUT -p icmp --icmp-type any -j ACCEPT\n-A INPUT -m state --state ESTABLISHED,RELATED -j ACCEPT\n-A INPUT -s 128.117.140.0/24 -j EDEX\n-A INPUT -s 128.117.156.0/24 -j EDEX\n-A INPUT -j EXTERNAL\n-A EXTERNAL -j REJECT\n-A EDEX -m state --state NEW -p tcp --dport 22 -j ACCEPT\n-A EDEX -m state --state NEW -p tcp --dport 5672 -j ACCEPT\n-A EDEX -m state --state NEW -p tcp --dport 9581 -j ACCEPT\n-A EDEX -m state --state NEW -p tcp --dport 9582 -j ACCEPT\n-A EDEX -j REJECT\nCOMMIT In this example, the IP range 128.117.140.0/24 will match all 128.117.140. addresses, while 128.117.156.0/24 will match 128.117.156. . Restart iptables service iptables restart For CentOS 7 error Redirecting to /bin/systemctl restart iptables.service\nFailed to restart iptables.service: Unit iptables.service failed to load: No such file or directory. The solution is: yum install iptables-services\nsystemctl enable iptables\nservice iptables restart",
"text":"vi /etc/sysconfig/selinux\n\n# This file controls the state of SELinux on the system.\n# SELINUX= can take one of these three values:\n# enforcing - SELinux security policy is enforced.\n# permissive - SELinux prints warnings instead of enforcing.\n# disabled - No SELinux policy is loaded.\nSELINUX=disabled\n# SELINUXTYPE= can take one of these two values:\n# targeted - Targeted processes are protected,\n# mls - Multi Level Security protection.\nSELINUXTYPE=targeted Read more about selinux at redhat.com reboot if necessary , required if iptables was updated.",
"title":"Disable SELinux"
},
{
"location":"/install/install-edex/#ssd-mount",
"text":"Though a Solid State Drive is not required, it is strongly encouraged in order to handle the amount of disk IO for real-time IDD feeds. The simplest configuration would be to mount an 500GB+ SSD to /awips2 to contain both the installed software (approx. 20GB) and the real-time data (approx. 150GB per day). The default purge rules are configured such that /awips2 does not exceed 450GB. /awips2/data_store is scoured every hour and should not exceed 50GB. If you want to increase EDEX data retention you should mount a large disk to /awips2/edex/data/hdf5 since this will be where the archived processed data exists, and any case studies created. Filesystem Size Used Avail Use% Mounted on\n /dev/sda1 30G 2.5G 26G 9% /\n tmpfs 28G 0 28G 0% /dev/shm\n /dev/sdc1 788G 81G 667G 11% /awips2\n /dev/sdb1 788G 41G 708G 10% /awips2/edex/data/hdf5",
"title":"SSD Mount"
},
{
"location":"/install/install-edex/#yum-install",
"text":"Download the script installEDEX.sh to setup and run yum to install AWIPS packages: wget http://www.unidata.ucar.edu/software/awips2/installEDEX.sh\nchmod 755 ./installEDEX.sh\n./installEDEX.sh What does installEDEX.sh do? Downloads awips2.repo or el7.repo to /etc/yum.repos.d/awips2.repo Runs yum clean all Runs yum groupinstall awips2-server",
"title":"yum install"
},
{
"location":"/install/install-edex/#edex-setup",
"text":"The command edex setup attempts to add the domain name of your server. /awips2/edex/bin/setup.env should contain the fully-qualified domain name, externally resolved, localhost will not work. export AW_SITE_IDENTIFIER=OAX\nexport EDEX_SERVER=edex-cloud.unidata.ucar.edu /awips2/ldm/etc/ldmd.conf contains the upstream server (default idd.unidata.ucar.edu , which requires you connect form a .edu domain). This file also contains the edexBridge hostname (default localhost ). EXEC \"pqact -e\"\nEXEC \"edexBridge -s localhost\" /etc/security/limits.conf defines the number of user processes and files (this step is automatically performed by installEDEX.sh ). Without these definitions, Qpid is known to crash during periods of high ingest. awips soft nproc 65536\nawips soft nofile 65536",
"title":"EDEX Setup"
},
{
"location":"/install/install-edex/#ldm",
"text":"EDEX installs its own version of the LDM to the directory /awips2/ldm . As with a the default LDM configuration, two files are used to control what IDD feeds are ingested: /awips2/ldm/etc/ldmd.conf - specifies an upstream LDM server to request data from, and what feeds to request: REQUEST NEXRAD3 \"./p(DHR|DPR|DSP|DTA|DAA|DVL|EET|HHC|N0Q|N0S|N0U|OHA|NVW|NTV|NST).\" idd.unidata.ucar.edu\nREQUEST FNEXRAD|IDS|DDPLUS|UNIWISC \".*\" idd.unidata.ucar.edu\nREQUEST NGRID \".*\" idd.unidata.ucar.edu\nREQUEST NOTHER \"^TIP... KNES.*\" idd.unidata.ucar.edu read more about ldmd.conf in the LDM User Manual /awips2/ldm/etc/pqact.conf - specifies the WMO headers and file pattern actions to request: # Redbook graphics\nANY ^([PQ][A-Z0-9]{3,5}) (....) (..)(..)(..) !redbook [^/]*/([^/]*)/([^/]*)/([^/]*)/([0-9]{8})\n FILE -overwrite -close -edex /awips2/data_store/redbook/\\8/\\4\\5Z_\\8_\\7_\\6-\\1_\\2_(seq).rb.%Y%m%d%H\n# NOAAPORT GINI images\nNIMAGE ^(sat[^/]*)/ch[0-9]/([^/]*)/([^/]*)/([^ ]*) ([^/]*)/([^/]*)/([^/]*)/ (T[^ ]*) ([^ ]*) (..)(..)(..)\n FILE -overwrite -close -edex /awips2/data_store/sat/\\(11)\\(12)Z_\\3_\\7_\\6-\\8_\\9_(seq).satz.%Y%m%d%H read more about pqact.conf in the LDM User Manual see available AWIPS LDM feeds",
"text":"to start all EDEX services, including the LDM: edex start\n\nStarting EDEX PostgreSQL: [ OK ]\nStarting httpd: [ OK ]\nStarting QPID [ OK ]\nStarting EDEX Camel (request): \nStarting EDEX Camel (ingest): \nStarting EDEX Camel (ingestGrib): \nStarting AWIPS LDM:The product-queue is OK. to stop: edex stop\n\nStopping EDEX Camel (request): \nStopping EDEX Camel (ingest): \nStopping EDEX Camel (ingestGrib): \nStopping QPID [ OK ]\nStopping httpd: [ OK ]\nStopping EDEX PostgreSQL: [ OK ]\nStopping AWIPS LDM:Stopping the LDM server... To manually start, stop, and restart: service edex_postgres start\nservice httpd-pypies start\nservice qpidd start\nservice edex_camel start The fifth service, edex_ldm , does not run at boot to prevent filling up disk space if EDEX is not running. ldmadmin start To start all services except the LDM (good for troubleshooting): edex start base To restart EDEX edex restart",
"text":"D2D (Display 2-Dimensions) is the default AWIPS CAVE perspective, designed to mimmic the look and feel of the legacy AWIPS I system. System menus include CAVE , File , View , Options , Tools , and Help (far right) Data menus include Models , Surface , NCEP/Hydro , Upper Air , Satellite , Radar , MRMS , and Maps . Frame control, map projection, image properties, and a few featured applications ( Warngen , Nsharp , Ncdata , and Browser ) make up the the primary D2D toolbar.",
"text":"At bottom-right of the map window the the Resource Stack, which displays all loaded resources and map overlays, and allows for interaction and customization with the resource via a right-click menu . There are three available views of the Resource Stack, the default will show all Product Resources. Right Click the mouse on the map background to switch to a Simple View. Right Click again to show all Map Resources. Right Click again to toggle back to Product Resources. It's important to understand that Product Resources and Map Resources are handled differently given the time-based nature of Products, compared to the static nature of maps. Selecting the Clear button will remove all Products but not remove any Map Products. Left-Click Resource Name to Hide A left click on any resource in the stack will hide the resource and turn the label gray. Clicking the name again makes the resource visible. Left-Click Background to Hide Resource Types A left click of the mouse anywhere on the map will hide the Resource Stack display names, which may help to declutter the view if a number of data types are loaded at once. Hold-Right-Click Background for Display Menu Holding down the right mouse button anywhere in the map view will open a right-click menu Show Map Legends From the above menu select Show Map Legends and watch the Resource Stack show only map resources which are loaded to the view. Toggle 2 or 4-Panel Layout Right-click hold in the view and select Two Panel Layout or Four Panel Layout to create duplicates of the current view (note that any data loaded to the view will be loaded to both displays within the view ). From this multi-pane display, hold-right-click again and you will see the Single Panel Layout option to switch back to a standard view (defaulting to the left of two, and top-left of four). Sample Loaded Resources Most data types have a right-click menu option for reading out the pixel value, displayed as multi-line text for multiple resources. Hold-Right-Click Resource Name for Menu Drag the mouse over a loaded resource and hold the right mouse button until a menu appears (simply clicking the resource with the right mouse button will toggle its visibility). The hold-right-click menu allows you to control individual resource Image Properties , Change Colormaps , change resource color, width, density, and magnification, move resources up and down in the stack, as well as configure custom options with other interactive resources.",
"text":"The Product Browser allows users to browse a complete data inventory in a side window, organized by data type. Selections for GFE , Grids , Lightning , Map Overlays , Radar , Satellite , Redbook , and VIIRS are available. All products loaded with the Product Browser are given default settings.",
"text":"This check button enables/disables the ability to select the time interval between frames of real-time or model data. This feature has the added benefit of allowing you to view extended amounts of data (temporally) but stay within the limits of 64 frames. For example, METAR surface plots, which typically display every hour, can be set to display every three hours via the Select Valid Time and Time Resolution Dialog Box. When the Time Options check button is selected, the next product you choose to display in the Main Display Pane launches either the Select Valid Time and Time Resolution dialog box or the Select\nOffset and Tolerance dialog box. When you are loading data to an empty display and the Time Options check button is enabled, the Select Valid Time and Time Resolution dialog box opens. Valid Time: In this column of dates/times, you may choose the one that will be the first frame loaded onto the Large Display Pane. The Default option is the most recent data. Time Resolution: This column contains various time increments in which the data can be displayed. Once you make a selection, the Valid Time Column indents the exact times that will\nbe displayed. The Default resolution displays the most recent frames available. With the Time Options check button enabled for a display that already contains data, when you choose the data to be overlaid in the Main Display Pane, the Select Offset and Tolerance dialog\nbox appears, providing the following options: Offset : This column contains various time increments at intervals before, at, or after the time you selected for the first product that is displayed in the Main Display Pane. Tolerance : The options in this column refer to how strict the time matching is. \"None\" means an exact match, while \"Infinite\" will put the closest match in each frame, regardless of how\nfar off it is.",
"text":"This check button enables/disables the ability to display data on its native scale. For example, if you enable Data Scaling and select a product from an alternate radar, the data will be displayed with that radar in the center of the screen. Other data can be overlaid on this \"dynamic\" scale until the Main Display Pane is cleared or a non-plan-view product is loaded.",
"text":"This check button enables/disables the ability to display two images at once. You can also enable/disable the ability to combine images by using the Toggle Image Combination iconified button on the Toolbar. Combined-image displays have been improved by removing the valid time for non-forecast products and removing the date string (time is kept) from the left side of the legend. In particular, this\nmakes All-Tilts radar legends more usable.",
"text":"Loop Properties is another dialog box that can be opened from the Options menu or from the Loop Properties iconified button on the D2D Toolbar, or by using the Ctrl + L keyboard shortcut. The dialog allows you to adjust the forward and backward speeds, with 0 = off and 10 = maximum speed. You can set the duration of the first and last frame dwell times to between zero and 2.5 seconds. You can turn looping on or off by checking the Looping check button. There is also a Looping button located on the Toolbar that enables/disables the animation in the large display pane. Finally, you can turn looping on and increase/decrease forward speed by pressing Page Up/Page Down on your keyboard, and turn looping off with the Left or Right Arrow keys. On the toolbar, you can use the button to start/stop looping.",
"text":"The Image Properties dialog box can be opened here or by using the Image Properties iconified button on the D2D Toolbar, or using using the Ctrl + I keyboard shortcut. This dialog box provides options that allow you to change the color table; adjust the brightness, contrast, and alpha of either a single image or combined images; fade between combined images; and/or interpolate the displayed data.",
"title":"Image Properties (Ctrl + I)"
},
{
"location":"/cave/d2d-perspective/#set-time",
"text":"This option allows you to set the CAVE clock, located on the bottom of the screen, to an earlier time for reviewing archived data.",
"text":"You can now set the background display color on your workstation. You can also set the background display color for a single pane via mouse Button 3 (B3).",
"text":"CAVE Perspective D2D is one of many available CAVE perspectives. By selecting the CAVE Perspective menu you can switch into the GFE , Hydro , Localization , MPE , or National Centers Perspective (which is available in the Other... submenu. Nobody seems to know why the NCP is not listed with the other perspectives, or how to make it appear with them).",
"text":"Preferences and settings for the CAVE client can be found in the CAVE Preferences menu. Set the Localization Site and server for the workstation; configure mouse operations, change performance levels, font magnification, and text workstation hostname.",
"title":"CAVE Preferences"
},
{
"location":"/cave/d2d-perspective/#load-mode",
"text":"Under the Display Properties option is Load Mode, which provides different ways to display data by manipulating previous model runs and inventories of data sets. The selected load mode is shown on the toolbar when the Load Mode menu is closed. A description of the Load Mode options follow. Latest : Displays forecast data only from the latest model run, but also backfills at the beginning of the loop with available frames from previous runs to satisfy the requested number of\nframes. Valid time seq : Displays the most recent data and fills empty frames with previous data. For models, it provides the product from the latest possible run for every available valid time. No Backfill : Displays model data only from the most recent model run time with no backfilling to fill out a loop. Using this Load Mode prevents the mixing of old and new data. Previous run : Displays the previous model run, backfilling with frames from previous runs at the beginning of the loop to satisfy the requested number of frames. Prev valid time seq : Displays the previous model run and fills empty frames with previous model data or analyses. Prognosis loop : Shows a sequence of n-hour forecasts from successive model runs. Analysis loop : Loads a sequence of model analyses but no forecasts. dProg/dt : Selects forecasts from different model runs that all have the same valid times. This load mode is available only when there are no other products loaded in the large display\npane. Forced : Puts the latest version of a selected product in all frames without time-matching. Forecast match : Overlays a model product only when its forecast times match those of an initially loaded product. This load mode is available only when another product is already\nloaded in the large display pane. Inventory : Selecting a product when the load mode is set to Inventory brings up a Dialog Box with the available forecast and inventory times from which you can select the product you\nwant. Inventory loads into the currently displayed frame. Slot : Puts the latest version of a selected product in the currently displayed frame.",
"title":"Load Mode"
},
{
"location":"/cave/maps-views-projections/",
"text":"Default Map Scales\n\uf0c1\n\n\nThe first toolbar menu item is a dropdown menu for different geographic areas and map projections. The efault view is always \nCONUS\n, which is a North Polar Steregraphic projection centered on the Continental United States.\n\n\nDefault projections and areas available in the menu\n\n\n\n\nN. Hemisphere\n (North Polar Stereographic)\n\n\nRegional\n (for the selected localization site)\n\n\nWFO\n (for the selected localization site)\n\n\nWorld Mercator\n\n\nWorld CED\n\n\nWorld Mollweide\n\n\nGeostationary (GOES East Full Disk)\n\n\nand \nRegional\n Mercator projections for \nAfrica\n, \nAustralia/NZ\n, \nSouth America\n, \nEurope\n, \nAlaska\n, \nHawaii\n, \nPuerto Rico\n, \nJapan\n, \nPacific Ocean\n, and the north and south poles.\n\n\n\n\nThere is also a \nWFO\n submenu which contains a map scale for every NWS localization site. \n\n\n\n\n\n\nNew Map Editor / View\n\uf0c1\n\n\nFile \n New Map\n\n\nOpens a new map editor tab with the default projection (CONUS Polar Stereographic). \n\n\n\n\nThis can also be done by \nright-click\n on any tab and selecting \nNew Editor\n\n\n\n\n\n\nNew Projection\n\uf0c1\n\n\nFile \n New Projection\n\n\nCreate a new map projection.",
"text":"The first toolbar menu item is a dropdown menu for different geographic areas and map projections. The efault view is always CONUS , which is a North Polar Steregraphic projection centered on the Continental United States. Default projections and areas available in the menu N. Hemisphere (North Polar Stereographic) Regional (for the selected localization site) WFO (for the selected localization site) World Mercator World CED World Mollweide Geostationary (GOES East Full Disk) and Regional Mercator projections for Africa , Australia/NZ , South America , Europe , Alaska , Hawaii , Puerto Rico , Japan , Pacific Ocean , and the north and south poles. There is also a WFO submenu which contains a map scale for every NWS localization site.",
"text":"File New Map Opens a new map editor tab with the default projection (CONUS Polar Stereographic). This can also be done by right-click on any tab and selecting New Editor",
"text":"AWIPS contains two methods for saving and loading data resources: \nBundles\n are a simple way to save loaded resources to access in future CAVE sessions. \nProcedures\n are similar to Bundles, but can be thought of a \ngroups of bundles\n and allows the user to manage saved resources with more control.\n\n\nBundles\n\uf0c1\n\n\nFile \n Open Bundle\n\uf0c1\n\n\nLoad a previously-saved bundle from within the AWIPS system. The Open Bundle dialog allows you to select your own saved bundles as well as those saved by other users (and other localization-levels such as \nworkstation\n).\n\n\nEach selected bundle will load its contents to new tabs which are named after the bundle file name (e.g. NAM_ThetaE)\n\n\n\n\nMost saved bundles will consist of a single Map Editor (tab), but with multiple tabs saved each will open again in its own Map Editor\n\n\n\n\nFile \n Save Bundle\n\uf0c1\n\n\nSave a product display within the AWIPS system, synching the bundle between CAVE and the EDEX server.\n\n\n\n\nFile \n Delete Bundle\n\uf0c1\n\n\nSelect and remove a saved bundle under File \n Delete Bundle. Select the file name and click \nOK\n and then confirm deletion to remove the saved file permanently.\n\n\n\n\n\n\n\n\nLoad Bundle from Local Disk\n\uf0c1\n\n\nTo load a previously-saved display from a path within the file directory of the workstation, select \nFile \n Open Bundle\n and then select the \nFile\n button on the right to browse your local directories.\n\n\n\n\n\n\nSave Bundle to Local Disk\n\uf0c1\n\n\nTo save a product display to a path within the file directory of the workstation, select \nFile \n Save Bundle\n and then select the \nFile\n button on the right.\n\n\n\n\nProcedures\n\uf0c1\n\n\nNew Procedure\n\uf0c1\n\n\n\n\nSelect the menu \nFile \n Procedures \n New\n\n\nSelect \nCopy Into\n to add all loaded resources to the Procedure Stack\n\n\nSelect \nSave\n (or \nSave As\n) and then enter a name for the Procedure before clicking \nOK\n to save.\n\n\n\n\n\n\nOpen Procedure\n\uf0c1\n\n\nSimilar to creating a new Procedure, select \nFile \n Procedures \n Open\n, select the saved resources and click \nLoad\n to load them to CAVE.\n\n\nDelete Procedure\n\uf0c1\n\n\nFrom the menu \nFile \n Procedures \n Delete\n you can delete existing Procedure files in a way similar to deleting saved Bundle files.",
"text":"Load a previously-saved bundle from within the AWIPS system. The Open Bundle dialog allows you to select your own saved bundles as well as those saved by other users (and other localization-levels such as workstation ). Each selected bundle will load its contents to new tabs which are named after the bundle file name (e.g. NAM_ThetaE) Most saved bundles will consist of a single Map Editor (tab), but with multiple tabs saved each will open again in its own Map Editor",
"text":"Select and remove a saved bundle under File Delete Bundle. Select the file name and click OK and then confirm deletion to remove the saved file permanently.",
"text":"To load a previously-saved display from a path within the file directory of the workstation, select File Open Bundle and then select the File button on the right to browse your local directories.",
"text":"To save a product display to a path within the file directory of the workstation, select File Save Bundle and then select the File button on the right.",
"text":"Select the menu File Procedures New Select Copy Into to add all loaded resources to the Procedure Stack Select Save (or Save As ) and then enter a name for the Procedure before clicking OK to save.",
"text":"Export Images\n\uf0c1\n\n\nFile \n Export \n Image\n\n\nwhich captures a screenshot of the current view\n\n\n\n\n\n\nExport KML\n\uf0c1\n\n\nFile \n Export \n KML\n\n\nThe \"Export\" submenu also includes a \"KML\" option, which allows users to save D2D displays or\nGFE grids in the KML (Keyhole Markup Language) file format. When zipped (compressed), the KML\nfile format forms a KMZ file, which can be used in applications such as Google Earth.\n\n\n\n\nThe KML dialog box includes options to select frames to export. This includes exporting all frames,\nthe current/displayed frame, a range of frames, and, in GFE, the selected time range as highlighted in\nthe Grid Manager. Additional options are available for selection under the \"Other Options\" section:\n\n\n\n\n\n\nExport Hidden\n: When selected, all displayed and hidden products listed in the Product Legend section of the Main Display Pane will be exported.\n\n\n\n\n\n\nExport Maps\n: When selected, all enabled maps displayed within the Main Display Pane will be\nexported.\n\n\n\n\n\n\nShade Earth\n: When selected, a shaded background is applied to the exported product. If loaded in Google Earth, the earth will be overlaid with a black backdrop, and data will be displayed as it would in D2D with a black background.\n\n\n\n\n\n\nShow Background Tiles\n: When selected, data (such as plot data) will display on top of black\ntiles when loaded in Google Earth.\n\n\n\n\n\n\n\n\nCAVE Import Formats\n\uf0c1\n\n\nCAVE supported the following geo-referenced data files. CAVE can import the following through formats through the \nCAVE\n -\n \nImport\n menu.\n\n\n\n\n\n\nGIS Data\n\n\n\n\n\n\nBCD File\n\n\n\n\n\n\nGeoTIFF\n\n\n\n\n\n\nLPI File\n\n\n\n\n\n\nSPI File\n\n\n\n\n\n\nDisplays\n\n\n\n\n\n\n\n\n\n\nCAVE Export Formats\n\uf0c1\n\n\nCAVE can export to the following through the \nCAVE\n -\n \nExport\n menu.\n\n\n\n\n\n\nKML\n\n\n\n\n\n\nEditor Display\n\n\n\n\n\n\nPerspective Display\n\n\n\n\n\n\nCapture Current Frame\n\n\n\n\n\n\nCapture All Frames\n\n\n\n\n\n\nPrint Screen",
"title":"Import/Export"
},
{
"location":"/cave/import-export/#export-images",
"text":"File Export Image which captures a screenshot of the current view",
"title":"Export Images"
},
{
"location":"/cave/import-export/#export-kml",
"text":"File Export KML The \"Export\" submenu also includes a \"KML\" option, which allows users to save D2D displays or\nGFE grids in the KML (Keyhole Markup Language) file format. When zipped (compressed), the KML\nfile format forms a KMZ file, which can be used in applications such as Google Earth. The KML dialog box includes options to select frames to export. This includes exporting all frames,\nthe current/displayed frame, a range of frames, and, in GFE, the selected time range as highlighted in\nthe Grid Manager. Additional options are available for selection under the \"Other Options\" section: Export Hidden : When selected, all displayed and hidden products listed in the Product Legend section of the Main Display Pane will be exported. Export Maps : When selected, all enabled maps displayed within the Main Display Pane will be\nexported. Shade Earth : When selected, a shaded background is applied to the exported product. If loaded in Google Earth, the earth will be overlaid with a black backdrop, and data will be displayed as it would in D2D with a black background. Show Background Tiles : When selected, data (such as plot data) will display on top of black\ntiles when loaded in Google Earth.",
"text":"CAVE supported the following geo-referenced data files. CAVE can import the following through formats through the CAVE - Import menu. GIS Data BCD File GeoTIFF LPI File SPI File Displays",
"text":"CAVE can export to the following through the CAVE - Export menu. KML Editor Display Perspective Display Capture Current Frame Capture All Frames Print Screen",
"title":"CAVE Export Formats"
},
{
"location":"/cave/localization-perspective/",
"text":"Localization Levels\n\uf0c1\n\n\nAWIPS uses a hierarchical system known as \nLocalization\n to configure many aspects of EDEX and CAVE, such as available menu items, color maps, and derived parameters. This system allows a user to override existing configurations and customize CAVE. For example, a \nUser-level\n localization file will supercede any similar file in a lower level (such as \nWorkstation\n or \nSite\n).\n\n\n\n\nThere are six \nlevels of localization\n, starting with the default \nBASE\n\n\n\n\nBASE\n - default\n\n\nRegion\n - a region may have many sites (generally unused)\n\n\nSite\n - a site may have many desks (required)\n\n\nDesk\n - a desk may have many workstations\n\n\nWorkstation\n - a workstation may have many users\n\n\nUser\n - highest level of localization, overrides all others\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\nLocalization Editor\n\uf0c1\n\n\nThe Localization Perspective acts as file editor for the XML, Python, and text files which customize the look and feel of CAVE. \n\n\nUsers may copy and add files to available directories at the \nWorkstation\n and \nUser\n levels.\n\n\nExamples of things that can be accessed through the perspective include (this list is not all-inclusive):\n\n\n\n\n\n\nNCP Predefined Areas, Color Maps and Style Rules\n\n\n\n\n\n\nD2D Volume Browser Controls\n\n\n\n\n\n\nD2D Bundles - Scales (WFO, State(s), etc.)\n\n\n\n\n\n\nCAVE Map Overlays, Color Maps and Style Rules\n\n\n\n\n\n\nGFE Tools and Utilities\n\n\n\n\n\n\n\n\nThe left panel contains a directory heirarchy of CAVE files for D2D, GFE, and NCP, which can be copied and edited as \nuser\n localization files.\n\n\n\n\nThere may be several versions of each file including \nBASE\n, \nCONFIGURED\n (GFE only), \nSITE\n, \nWORKSTATION\n, and \nUSER\n. Each file version is listed separately under the actual file name.\n\n\nThe \nFile Editor\n view opens the selected configuration file in an appropriate editor. For example, a Python file is opened in a Python editor, and an XML file is opened in an XML editor.\n\n\n--\n\n\nCustomizing CAVE Menus\n\uf0c1\n\n\nNavigate to \nCAVE\n \n \nMenus\n and select a submenu (e.g. \nsatellite\n). This directory lists all of the menu file contributions made by this data plugin. Most data menu directories will have an \nindex.xml\n file from which you can investigate the menu structure and made needed changes. \n\n\nSelecting a file such as \nindex.xml\n will show a sub-menu with a default localization level (typically \nBASE\n or \nCONFIGURED\n). Double-click this tab to open in the file editor (you may need to click \nSource\n at the bottom of the view to see the raw XML). Right-click this tab and select \nCopy To\n \n \nUser (awips)\n and you will see the file localization versions update with the new copy. Select this file to edit, and override, the existing version.\n\n\n--\n\n\nAdd new Predefined Area to NCP\n\uf0c1\n\n\nIn the Localization Perspective, navigate to \u2018\nNCEP - Predefined Area Menus\n\u2019, double-click \u2018\nAreaMenus.xml\n\u2019, and then right-click \u2018\nBASE\n\u2019 and select \u2018\nCopy To - User\n\u2019. You can also copy to \nDesk\n or \nWorkstation\n localization.\n\n\n\n\nYou will see a new \u2018\nUSER (username)\n\u2019 or \n\u2018WORKSTATION (name)\u2019 \nentry for the file \nAreaMenus.xml\n. \n\n\n \n\n\nDouble-click the new file and copy or create a new AreaMenuItem entry, such as a new CONUS Mercator projection called \nCONUS_Mercator\n:\n\n\nAreaMenuItem subMenuName=\"\" menuName=\"CONUS (Mercator)\"\n\n\n\nsource\nPREDEFINED_AREA\n/source\n\n\n\nareaName\nCONUS_Mercator\n/areaName\n\n\n\n/AreaMenuItem\n\n\n\n\n\n\nNowyoucaneithercopyandpostanexistingxmlareafile,orsimplecreateoneintheNCP.SwitchbacktotheNCP,andselect\u2018\nArea-World\n\u2019toloadaknownMercatorprojection.ZoomintothecontinentalUnitedStatesandthenfromthemenubarselect\u2018\nFile-SaveArea\n\u2019andnameit\nCONUS_Mercator\nsoitmatchesthenamestringg
"text":"AWIPS uses a hierarchical system known as Localization to configure many aspects of EDEX and CAVE, such as available menu items, color maps, and derived parameters. This system allows a user to override existing configurations and customize CAVE. For example, a User-level localization file will supercede any similar file in a lower level (such as Workstation or Site ). There are six levels of localization , starting with the default BASE BASE - default Region - a region may have many sites (generally unused) Site - a site may have many desks (required) Desk - a desk may have many workstations Workstation - a workstation may have many users User - highest level of localization, overrides all others",
"text":"The Localization Perspective acts as file editor for the XML, Python, and text files which customize the look and feel of CAVE. Users may copy and add files to available directories at the Workstation and User levels. Examples of things that can be accessed through the perspective include (this list is not all-inclusive): NCP Predefined Areas, Color Maps and Style Rules D2D Volume Browser Controls D2D Bundles - Scales (WFO, State(s), etc.) CAVE Map Overlays, Color Maps and Style Rules GFE Tools and Utilities The left panel contains a directory heirarchy of CAVE files for D2D, GFE, and NCP, which can be copied and edited as user localization files. There may be several versions of each file including BASE , CONFIGURED (GFE only), SITE , WORKSTATION , and USER . Each file version is listed separately under the actual file name. The File Editor view opens the selected configuration file in an appropriate editor. For example, a Python file is opened in a Python editor, and an XML file is opened in an XML editor. --",
"text":"Navigate to CAVE Menus and select a submenu (e.g. satellite ). This directory lists all of the menu file contributions made by this data plugin. Most data menu directories will have an index.xml file from which you can investigate the menu structure and made needed changes. Selecting a file such as index.xml will show a sub-menu with a default localization level (typically BASE or CONFIGURED ). Double-click this tab to open in the file editor (you may need to click Source at the bottom of the view to see the raw XML). Right-click this tab and select Copy To User (awips) and you will see the file localization versions update with the new copy. Select this file to edit, and override, the existing version. --",
"text":"In the Localization Perspective, navigate to \u2018 NCEP - Predefined Area Menus \u2019, double-click \u2018 AreaMenus.xml \u2019, and then right-click \u2018 BASE \u2019 and select \u2018 Copy To - User \u2019. You can also copy to Desk or Workstation localization. You will see a new \u2018 USER (username) \u2019 or \u2018WORKSTATION (name)\u2019 entry for the file AreaMenus.xml . Double-click the new file and copy or create a new AreaMenuItem entry, such as a new CONUS Mercator projection called CONUS_Mercator : AreaMenuItem subMenuName=\"\" menuName=\"CONUS (Mercator)\" \n\n source PREDEFINED_AREA /source \n\n areaName CONUS_Mercator /areaName /AreaMenuItem Now you can either copy and post an existing xml area file, or simple create one in the NCP. Switch back to the NCP, and select \u2018 Area - World \u2019 to load a known Mercator projection. Zoom in to the continental United States and then from the menu bar select \u2018 File - Save Area \u2019 and name it CONUS_Mercator so it matches the name string given in the above AreaMenuItem. You can switch back to the Localization Perspective to confirm that the file was saved. It will be viewable under NCEP - Predefined Areas and, in this example, be called CONUS_Mercator.xml . CAVE needs to be restarted in order for the new menu item to show up under the NCP Area menu. Switch to the new Area to confirm. On your workstation you can find the new USER localization files in ~/caveData find ~/caveData -name CONUS_Mercator.xml\n\n./etc/user/mjames/ncep/PredefinedAreas/CONUS_Mercator.xml\n./.localization/NCEP/Predefined Areas/CONUS_Mercator.xml",
"title":"Add new Predefined Area to NCP"
},
{
"location":"/cave/ncp-perspective/",
"text":"The National Centers Perspective (NCP)\n\uf0c1\n\n\nThe NCP toolbar includes two buttons to load \nData\n and \nBundles\n, respectively. The toolbar also include a \nClear\n button, \nZoom\n and \nUnzoom\n, and the \nNSHARP\n plugin.\n\n\n\n\n\n\nLoading Data\n\uf0c1\n\n\n\n\n\n\nClick the \"\n+Data\n\" button.\n\n\n\n\n\n\nSelect \nCategory\n, \nSource\n, \nGroup\n, and \nAttributes\n\n\n\n\n\n\nDouble-click the product, or select \"\nAdd\n\" and the data will load to CAVE with the default number of frames (Note: this makes time-matching more difficult. For time-matching multiple products, load as a \nBundle\n.)\n\n\n\n\n\n\n\n\nLatest Available Data Time\n or \nCycle Time\n is underneath the Attributes column at bottom-right.\n\n\n\n\nCreate a Bundle\n\uf0c1\n\n\nOpen the Resource Manager by:\n\n\n\n\n\n\nClick the \"\n+Bundle\n\" button on the toolbar\n\n\n\n\n\n\nPress the \nSpacebar\n\n\n\n\n\n\nPress the \"\nW\n\" key\n\n\n\n\n\n\nClick \nFile -\n New -\n Bundle\n.\n\n\n\n\n\n\n\n\n\n\nTimeline\n\uf0c1\n\n\nA timeline is displayed for available data. Here, the user may choose the dominant resource, number of frames, time range, reference time, etc. for the products to be displayed.\n\n\n\n\nClicking \"\nLoad\n\" will keep open the Resource Manager while the selected data layers are loaded to the map. \u201d\nLoad and Close\n\u201d will display data and close the Resource Manager.\n\n\n\n\nSave a Bundle\n\uf0c1\n\n\nIn AWIPS II CAVE, Bundles are organized within the Resource Manager GUI. Steps in the Bundle creation process are prompted with new GUI windows that are specific to the operation taking place, as you will see below.\n\n\n\n\n\n\nSelect resources for a Bundle (as in previous steps).\n\n\n\n\n\n\nClick the \"\nSave Bundle\n\".\n\n\n\n\n\n\nSelect or type-in your desired Group Name and Bundle name and click \"\nSave Bundle\n\".\n\n\n\n\n\n\n\n\nAfter saving a Bundle, its a good idea to confirm that it loads correctly. Select \"\nBundle\n\" -\n \u201c\nLoad Bundle\n\u201d to find your newly created Bundle.\n\n\nThe \"\nEdit Bundle\n\" button is available to make any changes while loading.\n\n\n\n\nManage Bundles\n\uf0c1\n\n\nThe third tab in the Resource Manager, titled \nManage Bundles\n can be used to do just that: modify, create, and delete existing Bundle Groups.\n\n\nAt the top left, there are 3 options: \nModify Bundle Group\n, \nCreate Bundle Group\n, and \nDelete Bundle Group\n.\n\n\nThe user can change the order of the Bundles within the Bundle Group, by clicking the \"\nMove Up\n\" and \u201c\nMove Down\n\u201d buttons on the right. A user can add Bundles to an existing Bundle Group by clicking the \u201c\nAdd Bundle\n\u201d button. A new Gui will pop up, allowing the user to select a Bundle that exists within a different Bundle Group or a current CAVE display.\n\n\nA Bundle may be renamed by clicking the \"\nRename Bundle\n\" button. Similarly, an Bundle may be removed from a specific Bundle Group by clicking the \u201c\nRemove Bundle\n\u201d button. NOTE: any changes made here must be saved by clicking the \u201c\nSave Bundle Group\n\u201d button on the left-hand side.\n\n\nDeleting an Bundle Group is a fairly straightforward action. First, click the \"\nDelete Bundle Group\n\" option on the top-left, then select the Bundle Group Group and Name to be deleted.\n\n\n\n\n\n\nEdit Data Sources\n\uf0c1\n\n\n\n\nSelection a Resource to edit allows you to update the number of frames, frame span, range and timeline form. The plugin name and grid name (\nGDFILE\n) can also be edited.\n\n\n\n\n\n\nEdit Resource Attributes\n\uf0c1\n\n\nUsing gridded data, selecting an Attribute to edit allows you to change the GEMPAK syntax used to define the resource.\n\n\n\n\n\n\nAdd a New Grid\n\uf0c1\n\n\n\n\n\n\nClick the \"\nBundle\n\" button and then open the \u201c\nManage Data\n\u201d tab.\n\n\n\n\n\n\nSelect the category (we will use \nGRID\n).\n\n\n\n\n\n\nSelect a model to copy as a template. In this example we select the base \"\nNAM-12km\n\" model.\n\n\n\n\n\n\nClick the \"\nCopy\n\"bu
"text":"The NCP toolbar includes two buttons to load Data and Bundles , respectively. The toolbar also include a Clear button, Zoom and Unzoom , and the NSHARP plugin.",
"title":"The National Centers Perspective (NCP)"
},
{
"location":"/cave/ncp-perspective/#loading-data",
"text":"Click the \" +Data \" button. Select Category , Source , Group , and Attributes Double-click the product, or select \" Add \" and the data will load to CAVE with the default number of frames (Note: this makes time-matching more difficult. For time-matching multiple products, load as a Bundle .) Latest Available Data Time or Cycle Time is underneath the Attributes column at bottom-right.",
"text":"Open the Resource Manager by: Click the \" +Bundle \" button on the toolbar Press the Spacebar Press the \" W \" key Click File - New - Bundle .",
"title":"Create a Bundle"
},
{
"location":"/cave/ncp-perspective/#timeline",
"text":"A timeline is displayed for available data. Here, the user may choose the dominant resource, number of frames, time range, reference time, etc. for the products to be displayed. Clicking \" Load \" will keep open the Resource Manager while the selected data layers are loaded to the map. \u201d Load and Close \u201d will display data and close the Resource Manager.",
"text":"In AWIPS II CAVE, Bundles are organized within the Resource Manager GUI. Steps in the Bundle creation process are prompted with new GUI windows that are specific to the operation taking place, as you will see below. Select resources for a Bundle (as in previous steps). Click the \" Save Bundle \". Select or type-in your desired Group Name and Bundle name and click \" Save Bundle \". After saving a Bundle, its a good idea to confirm that it loads correctly. Select \" Bundle \" - \u201c Load Bundle \u201d to find your newly created Bundle. The \" Edit Bundle \" button is available to make any changes while loading.",
"text":"The third tab in the Resource Manager, titled Manage Bundles can be used to do just that: modify, create, and delete existing Bundle Groups. At the top left, there are 3 options: Modify Bundle Group , Create Bundle Group , and Delete Bundle Group . The user can change the order of the Bundles within the Bundle Group, by clicking the \" Move Up \" and \u201c Move Down \u201d buttons on the right. A user can add Bundles to an existing Bundle Group by clicking the \u201c Add Bundle \u201d button. A new Gui will pop up, allowing the user to select a Bundle that exists within a different Bundle Group or a current CAVE display. A Bundle may be renamed by clicking the \" Rename Bundle \" button. Similarly, an Bundle may be removed from a specific Bundle Group by clicking the \u201c Remove Bundle \u201d button. NOTE: any changes made here must be saved by clicking the \u201c Save Bundle Group \u201d button on the left-hand side. Deleting an Bundle Group is a fairly straightforward action. First, click the \" Delete Bundle Group \" option on the top-left, then select the Bundle Group Group and Name to be deleted.",
"text":"Selection a Resource to edit allows you to update the number of frames, frame span, range and timeline form. The plugin name and grid name ( GDFILE ) can also be edited.",
"text":"Click the \" Bundle \" button and then open the \u201c Manage Data \u201d tab. Select the category (we will use GRID ). Select a model to copy as a template. In this example we select the base \" NAM-12km \" model. Click the \" Copy \" button underneath the GRID column. You can edit the new resource under \" Edit Resource Type \". Choose a name for the new resource (e.g. WRF ) In \" Edit Resource Parameters \", change the \u201c GDFILE= \u201d definition to match the name of the new model in the database (In this case we change GDFILE=NAM to GDFILE=WRF) . Click \" Create \" at the bottom of the window to finish. The new Resource now displays with a ( U ) next to the name, signifying a user-created item. In Attribute Groups , you can add attributes to a resource by clicking \" Edit \". Select the desired Attribute Set and click \" Add - \" to add it to the right column (You can hold the Ctrl key and select multiple Attributes.) Click \" Save \" and then \u201c Ok \u201d. In the \" Create Bundle \" tab, click \u201c New \u201d to see the new Resource.",
"text":"The NCP includes a configurable multi-pane display. As seen in the figure below, selecting the \"Multi-Pane\" check box extends the GUI window and displays additional options. Selecting the \" Multi-Pane Display \" checkbox enables the multi-pane builder. This new feature allows you to customize the number of panes you would like to display in AWIPS II CAVE. The \"Select Pane\" portion of the GUI allows you to load different products into each pane, which includes importing previously created bundles. Here are a few quick steps to creating a Multi-pane display in AWIPS II: Click the Multi-Pane checkbox in the Resource Manager Select the number of Rows and Columns you would like your data display to contain Select the precise pane in which you would like a specific product (i.e. Row 1, Column1) Choose a product through the Add button (See Data Selection above) Select a different cell in your multi-paned display in which you would like to display a product the user will need to load a separate product from the Resource Manager for each pane in the select pane layout Repeat step #4 Repeat the previous steps, until all of your panes have products queued up inside. Click \" Load \" and your multi-paned display will appear",
"text":"The Load Bundle tab in the Resource Manager can be used to load Bundles previously created by the user: The user should select name of the Group in which the desired Bundle is housed. After doing so, a list of available Bundles will appear in the centrally located \"Bundles\" pane. Selecting a Bundle will populate the pane on the right, which displays the contents of each Bundle, and also provides information on its Localization settings. Clicking \"Load\" or \u201cLoad and Close\u201d at the bottom of this window will load the saved Bundle. Before doing so, you can adjust things like Frames, dominant resources, time range, etc. in the \u201c Select Timeline \u201d section at the bottom of the window. Multiple Bundles can be selected and loaded all at once by simply hold the Ctl key and multi-selecting Bundles from the central pane, and then clicking either of the Load buttons. If multiple Bundles are loaded at once, they will each be displayed in different tabs in the CAVE interface. The order/arrangement of the Bundles will be mimicked in the order of the tabs when displayed in CAVE. Finally, the user may also edit an Bundle in this tab, simply by clicking the \" Edit \" button, and making desired changes in the GUI that pops up.",
"title":"Load Multiple Bundles"
},
{
"location":"/cave/nsharp/",
"text":"NSHARP\n\uf0c1\n\n\nNSHARP, which stands for the \nN\national Center \nS\nounding and \nH\nodograph \nA\nnalysis and \nR\nesearch \nP\nrogram, is an AWIPS plugin originally based on NAWIPS NSHAREP, SPCs \nBigSHARP\n sounding display tool, and the Python package \nSHARpy\n. \n\n\nNSHARP is available a number of ways in CAVE:\n\n\n\n\nFrom the \nD2D toolbar\n select the NSHARP icon\n\n\nFrom the \nUpper Air\n menu select \nNSHARP Soundings\n\n\nFrom the \nUpper Air\n menu select a station from the RAOB menus\n\n\nFrom the \nUpper Air\n menu select \nNUCAPS Soundings\n\n\nFrom within \nModels \n Volume Browser\n\n\nFrom the \nMaps\n menu select \nSounding Locs\n to \n\n\n\n\nNSHARP Configurations\n\uf0c1\n\n\nNSHARP has four configurations for use in different operational settings:\n\n\n\n\n\n\nSPC Wide\n - more insets and graphs at the expense of timeline/station inventory.\n\n\n\n\n\n\nD2D Skewt Standard\n - default for WFOs, larger SkewT with inventory, no Wind/Height, temperature advection, insets, or graphs.\n\n\n\n\n\n\nD2D Lite\n - Skew-T, table, and inventory only.\n\n\n\n\n\n\nOPC\n - Ocean Prediction Center display.\n\n\n\n\n\n\n\n\nIf you would like to interactively explore the different graphical areas in\nNSHARP\non the Web\n, see the\nNSHARP Interactive Overview\n\n\n\n\n\n\nTo change the NSHARP confiuguration:\n\n\n\n\nClick the \nConfigure\n button\n\n\nClick \nDisplay Pane Configuration\n (second from bottom)\n\n\nChoose configuration, apply, save, close\n\n\n\n\n\n\nSkew-T Display\n\uf0c1\n\n\nThe Skew-T display renders a vertical profile of temperature, dew point, and wind for RAOBs and model point soundings using a Skew-T Log-P diagram. Skew-T is the default upper air chart in AWIPS, and can be changed to \nturbulence display\n (\"T\") or an \nicing display\n (\"I\"). \n\n\nThe upper-left red box is linked to the cursor readout when over the SkewT chart, reported as temperature, dewpoint, wind direction and speed, pressure, height AGL, and RH of the trace.\n\n\nWindspeed vs Height and Inferred Temperature Advection\n\uf0c1\n\n\nThe windspeed vs height and inferred temperature advection with height plot (referred to by label \"iii\" in the NSHARP schematic images) is situated next to the SkewT to show the values at the same heights. Inferred temperature advection is from the thermal wind. Use the AWIPS-2 NSHARP Interactive Overview page for more information about the Skew-T display.\n\n\nHodograph Display\n\uf0c1\n\n\nThis panel contains the hodograph display from the sounding data (referred to by label \"iv\" in the NSHARP schematic images). The rings in the hodograph represent the wind speed in 20 knot increments. The hodograph trace uses different colors to highlight wind observations in 3 km height increments. This display also contains information such as the mean wind, Bunkers Left/Right Moving storm motion, upshear and downshear Corfidi vectors, and a user-defined motion. Use the AWIPS NSHARP Interactive Overview page for more information about the hodograph display.\n\n\nInsets\n\uf0c1\n\n\nIn the SPC Wide Screen Configuration there are four small insets beneath the hodograph containing storm-relative windspeed versus height, a Storm Slinky, Theta-E vs Pressure, Possible Watch Type, Thea-E vs Height, and storm-relative wind vectors (referred to by label \"v\" in the NSHARP schematic images). There are buttons in the NSHARP(D2D) control button tab that toggle the six possible contents in the four boxes. Use the AWIPS NSHARP Interactive Overview page for more information on the tables and a list/definition of the parameters available.\n\n\nTable Output Displays\n\uf0c1\n\n\nThe Table Output Displays (referred to by label \"vi\"intheNSHARPschematicimages)containsfivedifferentpagesofparametersrangingfromparcelinstabilitytostormrelativesheartoseverehazardspotential.UsetheAWIPSNSHARPInteractiveOverviewpageformoreinformationonthetablesandalist/definitionoftheparametersavailable.\n\n\nGraphs/Statistics\n\uf0c1\n\n\nIntheSPCWideScreenCon
"title":"NSHARP"
},
{
"location":"/cave/nsharp/#nsharp",
"text":"NSHARP, which stands for the N ational Center S ounding and H odograph A nalysis and R esearch P rogram, is an AWIPS plugin originally based on NAWIPS NSHAREP, SPCs BigSHARP sounding display tool, and the Python package SHARpy . NSHARP is available a number of ways in CAVE: From the D2D toolbar select the NSHARP icon From the Upper Air menu select NSHARP Soundings From the Upper Air menu select a station from the RAOB menus From the Upper Air menu select NUCAPS Soundings From within Models Volume Browser From the Maps menu select Sounding Locs to",
"title":"NSHARP"
},
{
"location":"/cave/nsharp/#nsharp-configurations",
"text":"NSHARP has four configurations for use in different operational settings: SPC Wide - more insets and graphs at the expense of timeline/station inventory. D2D Skewt Standard - default for WFOs, larger SkewT with inventory, no Wind/Height, temperature advection, insets, or graphs. D2D Lite - Skew-T, table, and inventory only. OPC - Ocean Prediction Center display. If you would like to interactively explore the different graphical areas in NSHARP on the Web , see the NSHARP Interactive Overview To change the NSHARP confiuguration: Click the Configure button Click Display Pane Configuration (second from bottom) Choose configuration, apply, save, close",
"title":"NSHARP Configurations"
},
{
"location":"/cave/nsharp/#skew-t-display",
"text":"The Skew-T display renders a vertical profile of temperature, dew point, and wind for RAOBs and model point soundings using a Skew-T Log-P diagram. Skew-T is the default upper air chart in AWIPS, and can be changed to turbulence display (\"T\") or an icing display (\"I\"). The upper-left red box is linked to the cursor readout when over the SkewT chart, reported as temperature, dewpoint, wind direction and speed, pressure, height AGL, and RH of the trace.",
"text":"The windspeed vs height and inferred temperature advection with height plot (referred to by label \"iii\" in the NSHARP schematic images) is situated next to the SkewT to show the values at the same heights. Inferred temperature advection is from the thermal wind. Use the AWIPS-2 NSHARP Interactive Overview page for more information about the Skew-T display.",
"title":"Windspeed vs Height and Inferred Temperature Advection"
},
{
"location":"/cave/nsharp/#hodograph-display",
"text":"This panel contains the hodograph display from the sounding data (referred to by label \"iv\" in the NSHARP schematic images). The rings in the hodograph represent the wind speed in 20 knot increments. The hodograph trace uses different colors to highlight wind observations in 3 km height increments. This display also contains information such as the mean wind, Bunkers Left/Right Moving storm motion, upshear and downshear Corfidi vectors, and a user-defined motion. Use the AWIPS NSHARP Interactive Overview page for more information about the hodograph display.",
"title":"Hodograph Display"
},
{
"location":"/cave/nsharp/#insets",
"text":"In the SPC Wide Screen Configuration there are four small insets beneath the hodograph containing storm-relative windspeed versus height, a Storm Slinky, Theta-E vs Pressure, Possible Watch Type, Thea-E vs Height, and storm-relative wind vectors (referred to by label \"v\" in the NSHARP schematic images). There are buttons in the NSHARP(D2D) control button tab that toggle the six possible contents in the four boxes. Use the AWIPS NSHARP Interactive Overview page for more information on the tables and a list/definition of the parameters available.",
"title":"Insets"
},
{
"location":"/cave/nsharp/#table-output-displays",
"text":"The Table Output Displays (referred to by label \"vi\" in the NSHARP schematic images) contains five different pages of parameters ranging from parcel instability to storm relative shear to severe hazards potential. Use the AWIPS NSHARP Interactive Overview page for more information on the tables and a list/definition of the parameters available.",
"title":"Table Output Displays"
},
{
"location":"/cave/nsharp/#graphsstatistics",
"text":"In the SPC Wide Screen Configuration there are two graphs boxes under the insets (referred to by label \"vii\" in the NSHARP schematic images), and they can display information on Enhanced Bulk Shear, Significant Tornado Parameter, Significant Hail Parameter (SHIP), Winter Weather, Fire Weather, Hail model (not implemented), and the Sounding Analog Retrieval System (SARS). There are buttons in the NSHARP(D2D) control button tab that toggle the six possible contents in the two boxes. Use the AWIPS NSHARP Interactive Overview page for more information on the tables and a list/definition of the parameters available.",
"title":"Graphs/Statistics"
},
{
"location":"/cave/nsharp/#sounding-inventory",
"text":"This section (referred to by label \"viii\" in the NSHARP schematic images) controls the inventory of the soundings that have been loaded for potential display in NSHARP. The different colors of the text represent variously that a sounding/station is being displayed, available for display, or not available for display. Use the AWIPS NSHARP Interactive Overview page for more information on how to use the sounding inventory and time line.",
"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 \n \nCounty Warning Areas\n to see coverages)\n\n\n\n\nSteps involved in using WarnGen in Unidata AWIPS CAVE 17.1.1\n\n\n\n\nLoad NEXRAD Display from the Radar menu.\n\n\nChoose a WFO site with active severe weather (LKZ is used in the video).\n\n\nRe-localize to this site in the CAVE \n Preferences \n 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 \n 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\n\n\nLoad NEXRAD level 3 display\n\uf0c1\n\n\nSelect the menu \nRadar\n \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 \n \nPreferences\n \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\"\nsectiontoredrawadefaultwarningpolygonorientedalongthestormmotiontrackandcontainingthestormcentroiddotforthemostrecentvolumescan.TheinitialpolygonmayhaveunhatchedareasthatwillberemovedfromthewarningduetocrossingCWAsornotmeetingareathresholdsinthecountyforinclusion.TheWarned/HatchedAreabuttonallowyoutopreviewthepolygonshapethatwillbeissued,soyoucanmakefurtheredits.\n\n\nMovingVertexPoints\n\uf0c1\n\n\nVerticescanbemovedbyclickinganddraggingwiththemouse.Thewarningpolygon,includingstippling,willupdateautomatically.\n\n\n\n\nWhenreshapingyourwarningpolygoninthismanner,thephilosophyistoincludeallareasthatareatriskofexperiencingsevereweathercoveredbythatwarningtype.Effectivepolygonsaccountforuncertaintyovertimeandtypicallywidendownstream.TherewillbealotoftrainingprovidedonStorm-BasedWa
"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":"Click on any NEXRAD Display station to load a two-pane Reflectivity/Velocity view.",
"title":"Select the nearest WSR-88D location"
},
{
"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":"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.",
"title":"Generate a Storm Motion Vector"
},
{
"location":"/cave/warngen/#restart",
"text":"Click the Reset button to clear all current polygons and vectors and reset the storm centroid marker.",
"title":"Restart"
},
{
"location":"/cave/warngen/#redrawing-a-polygon",
"text":"Select the Track button in the \"Redraw Box on Screen\" 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.",
"title":"Redrawing a Polygon"
},
{
"location":"/cave/warngen/#moving-vertex-points",
"text":"Vertices can be moved by clicking and dragging with the mouse. The warning polygon, including stippling, will update automatically. 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.",
"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":"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\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.",
"title":"Restoring a Polygon"
},
{
"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.",
"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.",
"text":"AWIPS ingest and display of GOES-16 (GOES-R) products is handled by contributions from the \nawips2-goesr\n plugin repository. As of Unidata AWIPS 17.1.1, the GOES-R decoder supports the ingest and display of NOAAport provisional products (currently on the NOTHER feed), as well as Level 2b netCDF files. A GOES-R Geostationary Lightning Mapper (GLM) decoder is also provided to handle sensor lightning observations.\n\n\nGOES-R products are accessible in the menu \nSatellite\n \n \nGOES-16 Provisional Products\n\n\n\n\n\n\nNOAAport Provisional Products\n\uf0c1\n\n\nLDM Pattern Action\n\uf0c1\n\n\nNOTHER ^(TI[RS]...) (KNES) (......) (...)\n FILE -close -edex\n /awips2/data_store/satellite/goes16/\\1_\\2_\\3_\\4_(seq).gini\n\n\n\nPuerto Rico sector (PRREGI)\n\uf0c1\n\n\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\nIcing Composite\n\uf0c1\n\n\nChannels 5,3,2 (1.61u, 0.87u, 0.64u)\n\n\n\n\nDaytime Composite 1\n\uf0c1\n\n\nChannels 2,5,14 (0.64u, 1.61u, 11.20u)\n\n\n\n\nDaytime Composite 2\n\uf0c1\n\n\nChannels 2,3,2 (0.64u, 0.87u, 0.64u)\n\n\n\n\n\n\nGOES-16 Composite Imagery NOT SUPPORTED on macOS\n\n\nOpenGL Shading Language limitations prevent multi-channel imagery from displaying correctly on Mac:\n\n\n\n\nIcing (1.61, 0.87, 0.64)\n\n\nDaytime Composite (0.64, 1.61, 11.20)\n\n\nDaytime Composite (0.64, 0.87, 0.64) \n\n\n\n\n\n\nTo display multi-channel composites requires CAVE for Linux or Windows.\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 PRREGI\ndrwxr-xr-x 18 awips fxalpha TCONUS\ndrwxr-xr-x 18 awips fxalpha TFD\ndrwxr-xr-x 18 awips fxalpha TMESO-1\ndrwxr-xr-x 18 awips fxalpha TMESO-2\n\n\n\n\n\nLevel 2+ Products\n\uf0c1\n\n\nLevel 2+ products are described as derived environmental variables which will be created and disseminated when GOES-16 is used operationally (compared to \nLevel 0\n, described as unprocessed instrument data at full resolution, and \nLevel 1b\n products, described as radiometric and geometric correction applied to produce parameters in physical units). \n\n\nUnidata does not currently have access to these products, but EDEX 17.1.1 can support their ingest if made available. \n\n\nRead more about GOES-R data levels...\n\n\nLevel 2+ Decoder Regular Expression\n\uf0c1\n\n\nFrom \n/awips2/edex/data/utility/common_static/base/distribution/goesr.xml\n\n\n^OR_ABI-L2-\\w{3,5}(C|F|M1|M2)-M[34]_G\\d\\d_s\\d{14}_e\\d{14}_c\\d{14}.nc$\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\nWhile Unidata is not currently distributing GLM products, you can \ndownload a sample netCDF file\n and copy it to \n/awips2/data_store/ingest/\n in order to test the decoding and display of GOES-R lightning data.\n\n\nIngest Sample Data\n\uf0c1\n\n\nRun the single command from your EDEX server to ingest a single-time sample data set:\n\n\nwget http://www.unidata.ucar.edu/software/awips2/OR_GLM-L2-LCFA_G16_s20170402339144.nc -P /awips2/data_store/ingest/\n\n\n\nDisplay GLM Lightning Data\n\uf0c1\n\n\nLoad GLM data from the menu \nSatellite\n \n \nGOES-16 Provisional\n \n \nGLM-Lightning\n. Data are displayable as \nFlash\n, \nEvent\n, and \nGroup\n and 1min, 5min, 15min, and 1hr intervals.\n\n\n\n\n\n\nDerived Motion Winds\n\uf0c1\n\n\nAt the bottom of the menu \nSatellite\n \n \nGOES-16 Provisional Products\n are sub-menus for GOES-16 Derived Motion Wind (DMW) products. Select the sub-menu \nGOES-Test\n and then region (CONUS, Full Disk, Mesoscale), and then select the wind product by level:\n\n\n\n\nBy Pressure\n\n\nBy Mandatory Levels\n\n\nBy Channel",
"text":"Level 2+ products are described as derived environmental variables which will be created and disseminated when GOES-16 is used operationally (compared to Level 0 , described as unprocessed instrument data at full resolution, and Level 1b products, described as radiometric and geometric correction applied to produce parameters in physical units). Unidata does not currently have access to these products, but EDEX 17.1.1 can support their ingest if made available. Read more about GOES-R data levels...",
"text":"NASA's SPoRT MSFC Earth Science Office has contributed plugins to decode GLM level2 products, displayed as point data in CAVE. While Unidata is not currently distributing GLM products, you can download a sample netCDF file and copy it to /awips2/data_store/ingest/ in order to test the decoding and display of GOES-R lightning data.",
"text":"Run the single command from your EDEX server to ingest a single-time sample data set: wget http://www.unidata.ucar.edu/software/awips2/OR_GLM-L2-LCFA_G16_s20170402339144.nc -P /awips2/data_store/ingest/",
"text":"Load GLM data from the menu Satellite GOES-16 Provisional GLM-Lightning . Data are displayable as Flash , Event , and Group and 1min, 5min, 15min, and 1hr intervals.",
"text":"At the bottom of the menu Satellite GOES-16 Provisional Products are sub-menus for GOES-16 Derived Motion Wind (DMW) products. Select the sub-menu GOES-Test and then region (CONUS, Full Disk, Mesoscale), and then select the wind product by level: By Pressure By Mandatory Levels By Channel",
"text":"The GIS application is accessed through the CAVE menu by first selecting the Import option, and then choosing GIS Data from the Import submenu. The GIS DataStore Parameters dialog is comprised of four sections: DataStore Type : This section contains a data field where you select a file type from the dropdown\nlist. Connection Parameters : This section contains a Directory data field where you can either select from a dropdown list or browse to a directory containing a set of map shapefiles. Clicking the Browse button opens the directory navigating/browser dialog, which allows you to navigate easily to the desired directory. After locating the desired directory, clicking the Connect button lists the available shapefiles. Load As : In this section the shapefiles can be loaded as a Map or as a Product. Descriptions of both follow. Map : When this radio button is selected, the selected shapefile displays as a map. Click and hold the middle mouse button to open a pop-up menu and select Show Map Legend to display the Map ID in the Legend area at the bottom of the display. Product : When this radio button is selected, the start and end date/time data fields become enabled. You can select a start and end date/time from the Calendar dialog. Clicking on the Calendar icon opens the Calendar dialog. Loading a shapefile with the Product radio button selected will return a shaded (color-filled) image of the Map Product. The Product ID will appear in the Legend area at the bottom of the display after selecting Show Product Legend from the middle mouse click pop-up menu. The map product displays with the model data when the valid time of the model data falls within the start/end time range selected for the map product in the GIS DataStore Parameters dialog. When the valid time of the model data falls outside the start/end time of the map product, the map product image does not display. Table : In this section you can select one of the shapefiles listed in the window for display. The selected file will be highlighted and the OK button at the bottom of the dialog will be enabled. Clicking the OK button closes the GIS DataStore Parameters dialog box and displays the selected map or map product.",
"text":"Using the Preferences dialog, you can modify certain GIS display attributes in CAVE without having the GIS application open. Access the GIS Viewer via CAVE Preferences GIS Viewer . The attributes that can be modified within CAVE apply to the map/map product image displayed on the Main Display Pane. They are: color of the highlights; highlight line style; highlight line width; and map product opacity. The button next to the name of the attribute displays a swatch of the current value. Selecting this button opens a dialog for modifying that attribute and redefining the default value. A description of each attribute follows. Highlight Color : This button opens a dialog that includes a color wheel and a color palette. Clicking the OK button after changing the color sets the new color for the highlight that appears around a selected area (via the Attributes dialog), and closes the dialog. The new color is then displayed on the swatch. Highlight Style : This button opens a menu displaying a set of lines of differing styles. Doubleclicking on the desired line style sets the new style for the highlight that appears around a selected area (via the Attributes dialog), and closes the menu. The new line style is then displayed on the swatch. Highlight Width : This button opens a menu displaying a set of lines of differing widths. Double-clicking on the desired line width sets the new width for the highlight that appears around a selected area (via the Attributes dialog), and closes the menu. The new line width is then displayed on the swatch. Product Opacity : This button opens the Set Opacity dialog for setting the default opacity level for GIS map product images. The dialog includes a swatch and a slider. Moving the slider increases or decreases the opacity level. Clicking the OK button sets the default level and closes the dialog. Beneath the four attributes are two buttons: Restore Defaults on the left and Apply on the right. The function of the Restore Defaults button is to restore \"all\" the attributes to their initial (default) values. Click this button only if you want to restore all attributes to their default values. If you accidentally click the Restore Defaults button, you will need to return to the attribute dialog(s) and redefine your desired values. Use the Apply button to save any changes you make to the default attribute settings. Wait until you are satisfied with all the values you have set, and then click the Apply button once to save all the changes. The values you set here for the attributes will then be applied to the GIS application as the new defaults.",
"text":"You have the ability to highlight specific areas of the displayed map or map product image, and to hide other areas. These functionalities are executed through the Attributes dialog , commonly referred to as the \"Attributes Table\" because of its tabular style. To access the Attributes dialog , click and hold middle mouse button 3 (B3) on the Map ID in the Legend area to open the pop-up menu. From the pop-up menu select the Display Attributes option to open the Attributes dialog. The Attributes dialog includes two menus, Annotation and Data, which allow you to control highlighting and visibility for both the displayed images and the information contained in the Attributes dialog. For each row of information on the Attributes dialog there is an associated map/map product image displayed on the Main Display Pane.",
"text":"To place a highlight around a selected area of the GIS display image and highlight the corresponding row on the Attributes dialog, click and hold B3 on the row you want to select. Check the Highlighted checkbox in the pop-up menu to activate highlighting. Multiple rows can be selected using Ctrl + B1 to select each row, which will highlight the selected row in blue. Then click and hold B3 on one of the selected rows; this will turn all selected blue rows dark gray and open the pop-up menu. After checking the Highlighted checkbox all selected rows will be highlighted yellow and a highlighted border surrounding all the areas on the map corresponding to those selected rows will be highlighted with the color setup in the Preferences dialog box.",
"text":"To unhighlight selected rows and associated highlighted borders around the areas of the image, click and hold B3 on the row or select multiple rows via Ctrl + B1 and then click and hold B3 to open the pop-up menu and uncheck the Highlighted checkbox.",
"text":"To remove all highlighted borders around the areas of the image and remove all yellow highlighted rows on the Attributes dialog, select the Clear Highlights option under the Annotation menu. If you are interested in a particular area but don't know the Feature ID, which is listed in the Attributes dialog, double-click on the area of interest on the image in the Main Display Pane and the corresponding row will be highlighted. Conversely, double-clicking on a particular row will place a highlighted border around the corresponding area on the image.",
"text":"To hide an area of the image displayed on the Main Display Pane, simply click and hold B3 on the row in the Attributes dialog corresponding to the area of interest. This will open a pop-up menu where you will uncheck the Visible checkbox to deactivate visibility for the selected area. If you want to hide multiple areas of the image, preselect the rows using Ctrl + B1 to highlight in blue the multiple selections; then click and hold B3 on one of the rows to open the pop-up menu. The deactivation of visibility will affect all areas corresponding to the selected rows. The areas of the image will disappear from the display and the selected row(s) on the Attributes dialog box will be shaded light gray.",
"text":"To return the hidden area(s) of the image to their original visible state, click and hold B3 on the corresponding gray-highlighted row to open the pop-up menu. On the pop-up menu, check the Visible checkbox. To return multiple areas to their original visual state, use Ctrl + B1 to select all corresponding gray-highlighted rows; and then click and hold B3 on one of the rows to open the pop-up menu. Checking the Visible checkbox will affect all the selected rows and corresponding areas of the image. The previously gray highlighted rows will return to their orginal nonhighlighted state.",
"text":"The Make All Visible option under the Annotation menu enables you to return \"all\" hidden areas to their original visible state. All gray highlighted rows on the Attributes dialog will be returned to their original nonhighlighted state.",
"text":"In the Attributes dialog (\"Attributes Table\"), the options under the Data menu allow you to customize the table based on which columns to display and how the table is to be sorted.",
"text":"To select which columns to display, select Data Select Columns... . Within the Select Columns dialog, you can select the column(s) you don't want displayed by\nfirst selecting the individual item(s) and then using the single arrow button to move the item\n(s) from the Displayed window to the Available window. Clicking the OK button saves the\nchange and removes the columns from the Attributes dialog. Use the double arrow button to\nmove all the items listed in the Displayed window to the Available window. By default, all available columns are displayed.",
"text":"Selecting the Sort option opens the Sort Order dialog. Within the Sort Order dialog, you can select a column from the dropdown list of displayed columns and select how you want the information in that column sorted. The other columns will adjust accordingly. Clicking the OK button (hidden in the Exhibit under the dropdown list) closes the Sort Order dialog and saves the change according to your selection. Clicking the Cancel button closes the dialog without making any changes to the Attributes Table.",
"text":"You can view a sample of a selected GIS data attribute directly on the Main Display Pane without having to open the Attributes dialog. To open the Select Sample Attribute submenu, click and hold B3 on the Map Product ID in the Legend area to open a pop-up menu and select the Select Sample Attribute option. On the Select Sample Attribute submenu select the value you want displayed and then click the OK button. Click and hold B3 anywhere on the Main Display Pane to open a pop-up menu and check the Sample checkbox to activate the sampling functionality. Then, hovering your cursor over any area of the Map Product image will display the sample for the selected attribute",
"title":"Displaying a Sample of GIS Data Attribute Values\\"
"text":"Once the GIS data is displayed, there are several ways to customize the displayed data from within the GIS application. All customizations originate by selecting from the pop-up menu. To open the pop-up menu, click and hold mouse Button B3 (B3) on the GIS displayed image or on the Map/Map Product ID in the Legend area and move the cursor to the option you want to modify.",
"title":"GIS Data and Display Customization from within the GIS Application"
},
{
"location":"/cave/d2d-gridded-models/",
"text":"The Volume Browser provides access to numerical models, other gridded data, and selected point data sources, such as RAOB, METAR, and Profiler. Through the Browser interface, you can choose the data source(s), field(s), plane(s), and point(s), and generate a customized list of model graphics or images for display.\n\n\nThe Volume Browser window is divided into four areas:\n\n\n\n\nThe Menu Bar along the top\n\n\nThe Data Selection Menus\n\n\nThe Product Selection List\n\n\nThe Load Buttons (Diff and Load) to load items from the Product Selection List\n\n\n\n\nEach area is then subdivided into menu components. The menu bar along the top of the Volume Browser window has dropdown lists that contain options for controlling all the various menu choices of the Volume Browser.\n\n\nVolume Browser Menu Bar\n\uf0c1\n\n\nThe dropdown menus in the Volume Browser menu bar contain options for controlling and manipulating the Volume Browser or the products chosen through the Volume Browser\n\n\n\n\nFile\n\n\nClone\n\n\nExit\n\n\n\n\n\n\nEdit\n\n\nClear All\n\n\nClear Sources\n\n\nClear Fields\n\n\nClear Panes\n\n\nSelect None\n\n\nSelect All\n\n\nFind (Ctrl+F)\n\n\n\n\n\n\n\n\nVB Tools\n\uf0c1\n\n\n\n\nBaselines\n\uf0c1\n\n\n\n\nSelecting Baselines displays 10 lines, labeled A-A' to J-J', along which cross-sections can be\nconstructed from within the Volume Browser. These baseline resources are \neditable\n.\n\n\nIf you are zoomed in over an area when you load baselines and none appear, press the middle mouse button (B3) to \"snap\" a baseline to where the mouse cursor is. The system chooses a baseline that has not been recently used. If you\nare working with a baseline, a second click with B3 will return you to the original baseline, even\nif you modified another baseline.\n\n\n\n\nPoints\n\uf0c1\n\n\n\n\nPoints are used to generate model soundings, time-height cross-sections, time series, and variable vs.\nheight plots using the Volume Browser. As with the Baselines, the locations of these Points can be\nedited in the following manner:\n\n\n\n\n\"Snapping\" an Interactive Point\n: If you are zoomed in over an area when you load Interactive\nPoints and no Points appear, click B3 to \"snap\" a Point to where the mouse cursor is positioned.\nThe system chooses a Point that has not been recently used. If you are currently working with a\nPoint, then a second B3 click will place another Point at the location of your cursor.\n\n\nDynamic Reference Map\n: When you generate a model sounding, a time-height cross-section, a\ntime series, or a variable vs. height plot, a small reference map indicating the location(s) of the\nplotted sounding(s) is provided in the upper left corner of the Main Display Pane.\n\n\n\n\nPoints may be created, deleted, hidden, and manipulated (location, name, font, and color). Points are\nnot limited in terms of number, location, or designation. Points may also be assigned to different\ngroups to facilitate their use.\n\n\nDisplay Types\n\uf0c1\n\n\n\n\nPlan View (default)\n\uf0c1\n\n\n\n\nThe default option for the Volume Browser. From the Plan-view perspective, data are plotted onto horizontal surfaces. The Plan view Planes are discussed in the planes section that follows. The additional options menu that appears in the Volume Browser menu bar allows you to choose whether you want the Plan view data to Animate in Time or Animate in Space.\n\n\n\n\nCross Section\n\uf0c1\n\n\n\n\nAllows you to view gridded data as vertical slices along specific baselines. You need to use either the Interactive Baseline Tool or the predefined latitude/longitude baselines to specify the slice you wish to see. One of the additional options menus that appear in the Volume Browser menu bar allows you to choose whether you want the cross-section data to animate in time or space, while the other options menu allows you to adjust the vertical resolution. Descriptions of these options follows. (Note that the Fields and Planes submenu labels have changed after selecting \"Cross section.\")\n\n\n\n\nTimeHeight\n\uf0c1\
"text":"The dropdown menus in the Volume Browser menu bar contain options for controlling and manipulating the Volume Browser or the products chosen through the Volume Browser File Clone Exit Edit Clear All Clear Sources Clear Fields Clear Panes Select None Select All Find (Ctrl+F)",
"title":"Volume Browser Menu Bar"
},
{
"location":"/cave/d2d-gridded-models/#vb-tools",
"text":"",
"title":"VB Tools"
},
{
"location":"/cave/d2d-gridded-models/#baselines",
"text":"Selecting Baselines displays 10 lines, labeled A-A' to J-J', along which cross-sections can be\nconstructed from within the Volume Browser. These baseline resources are editable . If you are zoomed in over an area when you load baselines and none appear, press the middle mouse button (B3) to \"snap\" a baseline to where the mouse cursor is. The system chooses a baseline that has not been recently used. If you\nare working with a baseline, a second click with B3 will return you to the original baseline, even\nif you modified another baseline.",
"title":"Baselines"
},
{
"location":"/cave/d2d-gridded-models/#points",
"text":"Points are used to generate model soundings, time-height cross-sections, time series, and variable vs.\nheight plots using the Volume Browser. As with the Baselines, the locations of these Points can be\nedited in the following manner: \"Snapping\" an Interactive Point : If you are zoomed in over an area when you load Interactive\nPoints and no Points appear, click B3 to \"snap\" a Point to where the mouse cursor is positioned.\nThe system chooses a Point that has not been recently used. If you are currently working with a\nPoint, then a second B3 click will place another Point at the location of your cursor. Dynamic Reference Map : When you generate a model sounding, a time-height cross-section, a\ntime series, or a variable vs. height plot, a small reference map indicating the location(s) of the\nplotted sounding(s) is provided in the upper left corner of the Main Display Pane. Points may be created, deleted, hidden, and manipulated (location, name, font, and color). Points are\nnot limited in terms of number, location, or designation. Points may also be assigned to different\ngroups to facilitate their use.",
"text":"The default option for the Volume Browser. From the Plan-view perspective, data are plotted onto horizontal surfaces. The Plan view Planes are discussed in the planes section that follows. The additional options menu that appears in the Volume Browser menu bar allows you to choose whether you want the Plan view data to Animate in Time or Animate in Space.",
"text":"Allows you to view gridded data as vertical slices along specific baselines. You need to use either the Interactive Baseline Tool or the predefined latitude/longitude baselines to specify the slice you wish to see. One of the additional options menus that appear in the Volume Browser menu bar allows you to choose whether you want the cross-section data to animate in time or space, while the other options menu allows you to adjust the vertical resolution. Descriptions of these options follows. (Note that the Fields and Planes submenu labels have changed after selecting \"Cross section.\")",
"text":"Used in conjunction with the Interactive Points Tool to enable you to view a time height cross section of a full run of gridded model data for a specific location. Additional options menus in the Volume Browser menu bar allow you to choose the direction in which you want the data to be plotted, and to adjust the vertical resolution.",
"text":"Enables you to view a profile of a meteorological model field as it changes through height, which is displayed in millibars. By using the Interactive Points Tool, you can select one or more locations from which to plot the data.",
"title":"Var vs Hgt"
},
{
"location":"/cave/d2d-gridded-models/#sounding",
"text":"Works in conjunction with the Interactive Points Tool to enable you to generate a Skew-T chart for a specific location, no additional menus appear in the Volume Browser when the Soundings setting is chosen.",
"text":"Used in conjunction with the Interactive Points Tool to enable you to plot gridded data on a time versus data value graph for a specified point.",
"text":"The default option for the Volume Browser. It allows you to view model data through time",
"title":"Time"
},
{
"location":"/cave/d2d-gridded-models/#space",
"text":"Allows you to loop through a series of predefined latitude or longitude cross-sectional slices at a fixed time.",
"title":"Space"
},
{
"location":"/cave/d2d-tools/",
"text":"These programs are accessible though the \nTools\n dropdown menu.\n\n\n\n\nMany of the tools listed under the Tools menu can be placed into an editable state. Do not enable the \"Hide Legends\" feature if you want to place a tool in an editable state, because access to editability is by clicking the center mouse button over the Product Legend\n\n\nAz/Ran Overlay\n\uf0c1\n\n\nThis tool displays a movable azimuth/range radar map overlay. The overlay is in the \"editable\" state when displayed, and can be relocated by clicking the right mouse button.\n\n\n\n\nBaselines\n\uf0c1\n\n\nSelecting Baselines displays 10 lines, labeled A-A' to J-J', along which cross-sections can be constructed from within the Volume Browser. Baselines come up editable.\n\n\n\"Snapping\" an Interactive Baseline: If you are zoomed in over an area when you load Interactive Baselines and no Baselines appear, press the right mouse button to \"snap\" a Baseline to where the mouse cursor is. The system chooses a Baseline that has not been recently used. If you are working with a Baseline, a second click with the right mouse button will return you to the original Baseline, even if you modified another Baseline in the meantime.\n\n\n\n\nChoose By ID\n\uf0c1\n\n\nChoose By ID, which is a function of DMD (Digital Mesocyclone Display), is a method of selecting feature locations. The tool is used to monitor the same feature at a certain location. Without the Choose By ID tool, a monitored feature (over a period of time) could move away from its monitored location and another feature could move in its place. You can use Choose By ID to set points, baselines, and \"Home\"forconventionallocationslikeMETARsandRAOBs(RadiosondeObservations),butitsprimaryuseisfortheWSR-88D-identifiedmesocyclonelocations.YoucanalsoaccesstheChooseByIDtoolfromtheToolsmenuontheVolumeBrowser.\n\n\n\n\nDistanceBearing\n\uf0c1\n\n\nSelectingthistooldisplayssixeditablelines,eachofwhichshowstheazimuthandrangeofthelabeledendofthelinerelativetotheunlabeledendoftheline.Youcanmakethelineseditablebyclickingthecentermousebuttonoverthelegendatthelowerrightofthedisplay.Onceineditmode,alinecanbemovedasaunitand/oreitherofitsendpointscanbeadjusted.\n\n\n\n\nDistanceSpeed\n\uf0c1\n\n\nThistoolcanbeusedtodeterminethespeedanddirectionofastormoranyothermeteorologicalfeatureofinterest.SelectingDistanceSpeeddisplaysaCentroidMarkertomovetothelocationofthestormorfeatureofinterestinanytwoormoreframesofdisplayedimagery(e.g.,asatelliteorradarloop).Thesystemthendisplaysastormtrackwiththedirection(degrees)andspeed(knots)ofmovement.WhenyouselecttheDistanceSpeedoption,theDistanceSpeeddialogboxopens.\n\n\n\n\n\n\n\n\nMode\n:Youhavethefollowingselectionsfromthisoption.\n\n\n\n\n\n\nPoint\n:AradiobuttonthatallowsyoutosettheCentroidMarkerasasinglepoint.\n\n\n\n\n\n\nPolyline\n:AradiobuttonthatallowsyoutosettheCentroidMarkerasapolyline.\n\n\n\n\n\n\n\n\n\n\nLegend\n:Youhavethefollowingselectionsfromthisoption.\n\n\n\n\n\n\nTime\n:AradiobuttonthatallowsyoutodisplaytimewiththeCentroidMarker.\n\n\n\n\n\n\nSpeed\n:AradiobuttonthatallowsyoutodisplayspeedwiththeCentroidMarker.\n\n\n\n\n\n\n\n\n\n\nDistanceScale\n\uf0c1\n\n\nThistoolcanbeusedtodeterminethesizeofastormoranyothermeteorologicalfeatureofinterest.\n\n\n\n\nFeatureFollowingZoom\n\uf0c1\n\n\nWhenyouzoominoverasmallareatobeabletoviewafeatureindetail,animationwilloftencausethefeaturetomoveintoandthenoutofthefieldofview.Thistoolallowsyoutofollowafeatureofinterestevenwhenzoomedintoasmallarea.\n\n\nTousethisfeature,first,youneedtoidentifythelocationandmotionofthefeature,usingDistanceSpeedortheWarnGentracker.Oncesatisfiedthatthetrackingiconisfollowingthefeatureofinterest,loadthistool,and
"title":"Display Tools"
},
{
"location":"/cave/d2d-tools/#azran-overlay",
"text":"This tool displays a movable azimuth/range radar map overlay. The overlay is in the \"editable\" state when displayed, and can be relocated by clicking the right mouse button.",
"title":"Az/Ran Overlay"
},
{
"location":"/cave/d2d-tools/#baselines",
"text":"Selecting Baselines displays 10 lines, labeled A-A' to J-J', along which cross-sections can be constructed from within the Volume Browser. Baselines come up editable. \"Snapping\" an Interactive Baseline: If you are zoomed in over an area when you load Interactive Baselines and no Baselines appear, press the right mouse button to \"snap\" a Baseline to where the mouse cursor is. The system chooses a Baseline that has not been recently used. If you are working with a Baseline, a second click with the right mouse button will return you to the original Baseline, even if you modified another Baseline in the meantime.",
"title":"Baselines"
},
{
"location":"/cave/d2d-tools/#choose-by-id",
"text":"Choose By ID, which is a function of DMD (Digital Mesocyclone Display), is a method of selecting feature locations. The tool is used to monitor the same feature at a certain location. Without the Choose By ID tool, a monitored feature (over a period of time) could move away from its monitored location and another feature could move in its place. You can use Choose By ID to set points, baselines, and \"Home\" for conventional locations like METARs and RAOBs (Radiosonde Observations), but its primary use is for the WSR-88D-identified mesocyclone locations. You can also access the Choose By ID tool from the Tools menu on the Volume Browser.",
"title":"Choose By ID"
},
{
"location":"/cave/d2d-tools/#distance-bearing",
"text":"Selecting this tool displays six editable lines, each of which shows the azimuth and range of the labeled end of the line relative to the unlabeled end of the line. You can make the lines editable by clicking the center mouse button over the legend at the lower right of the display. Once in edit mode, a line can be moved as a unit and/or either of its end points can be adjusted.",
"title":"Distance Bearing"
},
{
"location":"/cave/d2d-tools/#distance-speed",
"text":"This tool can be used to determine the speed and direction of a storm or any other meteorological feature of interest. Selecting Distance Speed displays a Centroid Marker to move to the location of the storm or feature of interest in any two or more frames of displayed imagery (e.g., a satellite or radar loop). The system then displays a storm track with the direction (degrees) and speed (knots) of movement. When you select the Distance Speed option, the Distance Speed dialog box opens. Mode : You have the following selections from this option. Point : A radio button that allows you to set the Centroid Marker as a single point. Polyline : A radio button that allows you to set the Centroid Marker as a polyline. Legend : You have the following selections from this option. Time : A radio button that allows you to display time with the Centroid Marker. Speed : A radio button that allows you to display speed with the Centroid Marker.",
"title":"Distance Speed"
},
{
"location":"/cave/d2d-tools/#distance-scale",
"text":"This tool can be used to determine the size of a storm or any other meteorological feature of interest.",
"text":"When you zoom in over a small area to be able to view a feature in detail, animation will often cause the feature to move into and then out of the field of view. This tool allows you to follow a feature of interest even when zoomed in to a small area. To use this feature, first, you need to identify the location and motion of the feature, using Distance Speed or the WarnGen tracker. Once satisfied that the tracking icon is following the feature of interest, load this tool, and the center of the zoom area will track with the Distance Speed icon. Toggling the overlay off will resume the standard zooming behavior, and toggling it back on will reinvoke the feature following zoom.",
"text":"Selecting the Time Of Arrival / Lead Time option displays a tracking line from a feature's initial starting point in a past frame to its final position in the current frame. Once the final position is set, an Arrival Point is displayed. You can drag this point anywhere along the line to get the Time Of Arrival / Lead Time and Distance. You can also change the Mode from Point to Circular Front or Polyline anywhere along the line to better represent the feature(s).",
"title":"Time of Arrival / Lead Time"
},
{
"location":"/cave/d2d-tools/#home",
"text":"Selecting the Home option displays a marker, which is an \"X\" with the word \"Home\" next to it.\nClicking on the Home Location Legend with the center mouse button makes the marker editable; drag the \"X\" or click with the right mouse button to change its location. When the Home Marker is displayed, use the Sample feature (clock and hold while moving the pointer around the screen) to display the range in miles and azimuth (in degrees) of the pointer location relative to the Home location.",
"title":"Home"
},
{
"location":"/cave/d2d-tools/#points",
"text":"The Points option initially displays a circular 10-point pattern, labeled A through J on the Map display. Points are used to generate model soundings, time-height cross-sections, time series, and variable vs. height plots using the Volume Browser. As with the Baselines, the locations of these Points can be edited in the following manner: \"Snapping\" an Interactive Point : If you are zoomed in over an area when you load Interactive\nPoints and no Points appear, click the right mouse button to \"snap\" a Point to where the mouse cursor is positioned. The system chooses a Point that has not been recently used. If you are currently working with a Point, then a second right mouse button click will place another Point at the location of your cursor. Dynamic Reference Map : When you generate a model sounding, a time-height cross-section, a\ntime series, or a variable vs. height plot, a small reference map indicating the location(s) of the\nplotted sounding(s) is provided in the upper left corner of the Main Display Pane. Points may be created, deleted, hidden, and manipulated (location, name, font, and color). Points are not limited in terms of number, location, or designation. Points may also be assigned to different groups to facilitate their use. Once the Points tools have been loaded, the addition, deletion, or manipulation of Points can be accomplished in three ways: Create Point Dialog Box : The Create Point dialog box is opened by clicking and holding the right mouse button on the map (but not on any exisiting Point) and selecting the \"New Point...\" option. The Create Point dialog box opens with the Lat and Lon text boxes populated with the latitude\nand longiture values at the point where you had clicked the right mouse button. The latitude and longitude values can be viewed in \"Degrees : Minutes : Seconds,\" \"Degrees : Minutes,\" or \"Degrees Only\" (N and S refer to North and South; W and E refer to West and East). In the Create Point dialog box, you must: Enter the Point's name Modify the latitude and longitude values Assign the Point's color and font use Assign the Point to a group Select whether the Point is movable or hidden By default, individual Points do not have an assigned color. They inherit the color\nof the Interactive Points layer reflected in the Interactive Points product legend. You can\nchange the color of the Interactive Points layer by right clicking on the Interactive Points\nproduct legend and selecting a color from the dropdown list. The selected color then\nchanges all points not having an assigned color to the new color. Points can be assigned to \" ,\" which will organize them in the root location containing the group names when accessed by the Edit Points dialog box (see below). Edit Point Dialog Box : The Edit Point dialog box is opened by clicking and holding the right mouse button on a Point on the map and selecting the \"Edit Point...\" option. The latitude and longitude values can be viewed in \"Degrees : Minutes : Seconds,\" \"Degrees : Minutes,\" or \"Degrees Only\" (N and S refer to North and South; W and E refer to West and East). Besides the option of selecting the Edit Points dialog box, you also have the option\nof selecting \"Hide Point,\" \"Delete Point,\" or \"Move Point.\" Once hidden, the Point can be\nunhidden using the Points List dialog box, where you would uncheck the checkbox under\nthe \"Hidden\" column adjacent to the Point that was hidden (see below). If \"Delete Point\" is\nselected, a pop-up opens to confirm whether you want to delete the Point. Selecting the\n\"Move Point\" option moves the Point to wherever you place the cursor on the map. Points List Dialog Box : The Points List dialog box is opened by clicking and holding the right mouse button on the Interactive Points product legend and selecting the \"Edit Points...\"option.ThePointsListdialogboxlistsalltheavailablegroupsandPoints.Groupscanbeexpandedto\nreviewthelistofPointsassignedtothatgroupbyclickingthearrownexttothe
"title":"Points"
},
{
"location":"/cave/d2d-tools/#put-home-cursor",
"text":"The Put home cursor tool provides an easy way to locate a METAR observation station, a city and\nstate, or a latitude/longitude coordinate. For Canada and Mexico, only the METAR observation stations and latitude/longitude coordinates are accessible. When you select Put home cursor from the Tools dropdown menu, the Home marker X is displayed and the Put Home Cursor dialog box opens. You can use the Home marker, as previously described in the Home Tool, and the new Home location\n(station, city/state, or latitude/longitude) is identified in the Put Home Cursor dialog box.\nAnother way to use this tool is to type in the station, city and state, or latitude and longitude, and select Go, or hit Enter on the keypad, to move the Home marker to the specified location. The new location's nearest METAR site, city and state, and latitude and longitude appear in the Put Home Cursor dialog box. The Put Home Cursor dialog box contains the following options. Location Selection : There are three ways to find a desired location. Once you choose the\nStation, City/State, or Lat/Lon radio button, an Entry Box is activated next to the respective label within the Put Home Cursor dialog box. Enter the desired location information. Go : This menu button initiates the search for the desired station, city/state, or latitude/longitude. The Home marker jumps to the newly specified location.",
"title":"Put home cursor"
},
{
"location":"/cave/d2d-tools/#range-rings",
"text":"The Range Rings Tool displays adjustable range rings around locations of interest to your local office. When you select Range Rings from the Tools dropdown menu, the Range Rings legend appears in the Main Display Pane. The tool comes up editable, and the rangeRing dialog box opens. (Clicking B2 over the legend toggles tool editability and closes/opens the rangeRing dialog box.) Within this dialog box, you can toggle on/off any of the target locations using the square selectors. Adjust the size of the radii (in nautical miles) by typing a new value in the entry boxes associated with each location and pressing the Apply button. You can also add labels at the center of the range ring and/or at any of the radial distances using the Labels Options menu associated with each location. Using the Movable Rings, you can add a new location at a specific point by using the Interactive Points Tool, or by typing in latitude/longitude coordinates. There is no practical limit on the number of new locations you can add to the display. The list of locations is pre-set but can be customized at a field site",
"title":"Range Rings"
},
{
"location":"/cave/d2d-tools/#sunsetsunrise",
"text":"By typing a date, as well as the latitude and longitude of a location into the Sunrise/Sunset Tool dialog box, you can obtain the time (for any time zone) of sunrise and sunset, as well as the total length of daylight for that date. Additional features include the ability to calculate the sunrise/sunset in a different hemisphere, and the azimuthal angles, relative to true north, of the sunrise and sunset.",
"title":"Sunset/Sunrise"
},
{
"location":"/cave/d2d-tools/#text-window",
"text":"Selecting this option brings up a Text Display window that behaves in the same way, except for scripts, as a window on the Text Workstation.",
"title":"Text Window"
},
{
"location":"/cave/d2d-tools/#units-calculator",
"text":"This tool converts the units of the first column into differing units of the second column. The units are grouped into temperature, velocity, distance, time, and atmospheric pressure. First, simply type the number and select the units of the value you wish to convert in the firstcolumn entry box. Then in the second column, select the desired units to which you want the original value converted. The new value will appear in the second column entry box.",
"title":"Units Calculator"
},
{
"location":"/cave/d2d-tools/#text-workstation",
"text":"",
"title":"Text Workstation"
},
{
"location":"/cave/d2d-radar-tools/",
"text":"These programs are accessible though the \nTools\n dropdown menu, and in individual site radar menus.\n\n\nEstimated Actual Velocity (EAV)\n\uf0c1\n\n\nA velocity (V) display from the radar shows only the radial component of the wind, so the indicated\nspeed depends on the direction of the wind and the azimuth (direction) from the radar. Consider, for example, a north wind. Straight north of the radar, the full speed of the wind will be seen on the V product. As one moves around to the east of the radar, the radial component gets smaller, eventually reaching zero straight east of the radar. If the wind direction is known, then the actual wind speed can be computed by dividing the observed radial speed by the cosine of the angle between the radar radial and the actual direction. The EAV tool allows you to provide that angle and use the sampling function of the display to show the actual wind speed.\n\n\n\n\nV-R Shear\n\uf0c1\n\n\nThis tool is used in conjunction with Doppler velocity data to calculate the velocity difference (or \"shear\") of the data directly under the end points. As with the Baselines, this feature comes up editable and the end points can be dragged to specific gates of velocity data. When in place, the speed difference (kts), distance between end points (nautical miles), shear (s-1), and distance from radar (Nmi) are automatically plotted next to the end points and in the upper left corner of the Main Display Pane. A positive shear value indicates cyclonic shear, while a negative value indicates anticyclonic shear. If either end point is not directly over velocity data, the phrase \"no data\" is reported for the shear value. This tool is also useful in determining gate-to-gate shear. Simply place the two end points directly over adjacent gates of velocity data.\n\n\n\n\n\"Snapping\" VR Shear\n: If you are zoomed in over an area when you load VR - Shear, and the VR - Shear Baseline does not appear, click the right mouse button to \"snap\"theBaselinetowherethemousecursorislocated.\n\n\nVR-Shearin4Panel\n:YoucanusetheVR-ShearToolwhenthelargedisplayisin4panel\nmode.TheVR-Shearoverlayisloadedindifferentcolorsforeachpanel.Thereareactually\nfourcopiesoftheprogramrunning,andeachbehavesindependently.Thismeansthatyoucan\ngetaccuratereadingsinanyoneofthefourpanels\u2014oneVR-Shearpaneliseditableatatime.Toactivate,clickthecentermousebuttonontheVR-Shearlegendinthedesiredpanelandpositionthequerylinetotheechoesofinterest.\n\n\n\n\nRadarDisplayControls\n\uf0c1\n\n\n\n\n\n\n\n\nTheRadarDisplayControlsdialogboxisderivedfromtheRadarToolssubmenuprovidesoptionsthatcontroltheappearanceoftheStormTrackInformation(STI),theHailIndex(HI),theTornadoVortexSignature(TVS),andtheDigitalMesocycloneDisplay(DMD)products,alongwithStorm\nRelativeMotion(SRM)options.TheRadarDisplayControlsdialogboxoptionsaredescribedbelow.\n\n\nTheRadarDisplayControlsdialogboxisdividedintosixsections:STI,HI,TVS,DMD/MD/TVS,DMD,andSRM.Eachsectionhasthefollowingoptions:\n\n\nSTI(StormTrackInformation)\n\uf0c1\n\n\nThissectionhasoptionstoadjusttheappearanceoftheSTIgraphicproduct.\n\n\n\n\n\n\nNumberofstormstoshow\n:Thissliderbarletsyouchoosethemaximumnumberofstorms(0to100)youwishtodisplayontheSTIproduct.Thedefaultvalueis20storms.\n\n\n\n\n\n\nTypeoftracktoshow\n:Thisoptionsmenuallowsyoutochoosethetypeofstormtrackthatyouwantdisplayed.\n\n\n\n\n\n\nHI(HailIndex)\n\uf0c1\n\n\nThisportionoftheRadarDisplayControlsdialogboxcontainsoptionsthataltertheappearanceoftheHIradargraphicproduct.YoucansetthelowandhighalgorithmthresholdsoftheProbabilityofHail(POH)andtheProbabilityofSevereHail(POSH).StormsthatmeetthelowPOHthresholdareindicatedbysmallopentriangles,whilesmallsolidtrianglesmarkthosethatmeetthehighPOHthreshold.Similarly,larg
"text":"A velocity (V) display from the radar shows only the radial component of the wind, so the indicated\nspeed depends on the direction of the wind and the azimuth (direction) from the radar. Consider, for example, a north wind. Straight north of the radar, the full speed of the wind will be seen on the V product. As one moves around to the east of the radar, the radial component gets smaller, eventually reaching zero straight east of the radar. If the wind direction is known, then the actual wind speed can be computed by dividing the observed radial speed by the cosine of the angle between the radar radial and the actual direction. The EAV tool allows you to provide that angle and use the sampling function of the display to show the actual wind speed.",
"title":"Estimated Actual Velocity (EAV)"
},
{
"location":"/cave/d2d-radar-tools/#v-r-shear",
"text":"This tool is used in conjunction with Doppler velocity data to calculate the velocity difference (or \"shear\") of the data directly under the end points. As with the Baselines, this feature comes up editable and the end points can be dragged to specific gates of velocity data. When in place, the speed difference (kts), distance between end points (nautical miles), shear (s-1), and distance from radar (Nmi) are automatically plotted next to the end points and in the upper left corner of the Main Display Pane. A positive shear value indicates cyclonic shear, while a negative value indicates anticyclonic shear. If either end point is not directly over velocity data, the phrase \"no data\" is reported for the shear value. This tool is also useful in determining gate-to-gate shear. Simply place the two end points directly over adjacent gates of velocity data. \"Snapping\" VR Shear : If you are zoomed in over an area when you load VR - Shear, and the VR - Shear Baseline does not appear, click the right mouse button to \"snap\" the Baseline to where the mouse cursor is located. VR - Shear in 4 Panel : You can use the VR - Shear Tool when the large display is in 4 panel\nmode. The VR - Shear overlay is loaded in different colors for each panel. There are actually\nfour copies of the program running, and each behaves independently. This means that you can\nget accurate readings in any one of the four panels \u2014 one VR - Shear panel is editable at a time. To activate, click the center mouse button on the VR - Shear legend in the desired panel and position the query line to the echoes of interest.",
"text":"The Radar Display Controls dialog box is derived from the Radar Tools submenu provides options that control the appearance of the Storm Track Information (STI), the Hail Index (HI), the Tornado Vortex Signature (TVS), and the Digital Mesocyclone Display (DMD) products, along with Storm\nRelative Motion (SRM) options. The Radar Display Controls dialog box options are described below. The Radar Display Controls dialog box is divided into six sections: STI, HI, TVS, DMD/MD/TVS, DMD, and SRM. Each section has the following options:",
"text":"This section has options to adjust the appearance of the STI graphic product. Number of storms to show : This slider bar lets you choose the maximum number of storms (0 to 100) you wish to display on the STI product. The default value is 20 storms. Type of track to show : This options menu allows you to choose the type of storm track that you want displayed.",
"text":"This portion of the Radar Display Controls dialog box contains options that alter the appearance of the HI radar graphic product. You can set the low and high algorithm thresholds of the Probability of Hail (POH) and the Probability of Severe Hail (POSH). Storms that meet the low POH threshold are indicated by small open triangles, while small solid triangles mark those that meet the high POH threshold. Similarly, large open triangles or solid triangles are plotted for the POSH low and high thresholds, respectively. Low hail probability (POH) : The storms that meet or exceed the threshold are indicated by small open triangles. The default setting is 30. Low severe hail probability (POSH) : The storms that meet or exceed the threshold are indicated by large open triangles. The default setting is 30. High hail probability : The storms that meet or exceed the threshold are indicated by small solid triangles. The default setting is 50. High severe hail probability : The storms that meet or exceed the threshold are indicated by small solid triangles. The default setting is 50.",
"text":"There is one option in this section of the Radar Display Controls dialog box. Show elevated TVS : This toggle button lets you control the appearance of the elevated TVS radar graphic product.",
"title":"TVS (Tornado Vortex Signature)"
},
{
"location":"/cave/d2d-radar-tools/#dmd-md-tvs",
"text":"There is one option in this section of the Radar Display Controls dialog box.\nShow extrapolated Features: With this option, you can choose whether to show the time-extrapolated\nfeatures using DMD, MD, or TVS.",
"title":"DMD, MD, TVS"
},
{
"location":"/cave/d2d-edit-menus/",
"text":"Any of the data menus can be customized in the Localization Perspective. \n\n\nChanging the models displayed with D2D bundles\n\uf0c1\n\n\n\n\n\n\nIn the Localization Perspective you can navigate to \nD2D\n \n \nVolume Browser\n \n \nVbSources\n and click on \nvolume.xml\n to expand. Then right-click on \nBASE\n and select \nCopy To...\n \nUser\n (awips).\n\n\n\n\n\n\nYou can then right-click again on the \nVbSources\n folder and select \nRefresh\n to see your new localization file called \nUSER (awips)\n. \n\n\n\n\n\n\nOpen the file and add or edit the model names: \n\n\nmenuContributionFile\n\n \ninclude installTo=\"menu:models\" \n fileName=\"menus/volume/allFamilies.xml\"\n\n \nsubstitute key=\"modelName\" value=\"CMC\" /\n\n \nsubstitute key=\"menuName\" value=\"CMC\" /\n\n \nsubstitute key=\"frameCount\" value=\"41\" /\n\n \nsubstitute key=\"TP\" value=\"TP\"/\n\n \n/include\n\n \ninclude installTo=\"menu:models\" \n fileName=\"menus/volume/allFamilies.xml\"\n\n \nsubstitute key=\"modelName\" value=\"DGEX\" /\n\n \nsubstitute key=\"menuName\" value=\"DGEX\" /\n\n \nsubstitute key=\"frameCount\" value=\"41\" /\n\n \nsubstitute key=\"TP\" value=\"TP\"/\n\n \n/include\n\n ...\n\n\n\n\n\n\n\nNotice that you specify both the \nmodelName\n (what it's named inside EDEX, such as NAM12), and \nmenuName\n, if you prefer a more detailed menu entry, such as \"NAM 12km\". When you are finished, save the file and restart CAVE for the changes to take effect.\n\n\nYour new localization file exists on the EDEX server (assuming username awips) as\n\n/awips2/edex/data/utility/cave_static/users/awips/volumebrowser/VbSources/index.html\n\n\nand will exist on the local CAVE machine under \n~/caveData/etc/user/awips/volumebrowser/VbSources/index.html\n\n\nRemoving menus from the menubar\n\uf0c1\n\n\nThis example covers how to remove a menu (in this case \nMRMS\n) from D2D:\n\n\n\n\nswitch to the Localization Perspective\n\n\nfind the \nmrms\n folder under CAVE \n Menus\n\n\ndouble-click to expand \nindex.html\n\n\nright-click \nBASE\n and select \nCopy To...\n, then select \nUSER\n level\n\n\nright-click refresh the \nmrms\n entry\n\n\n\n\ndouble click \nUSER\n to open the editor and change\n\n\nmenuContributionFile\n\n \ninclude installTo=\"menu:mrms?after=MRMS_MENU_START\"\n fileName=\"menus/mrms/mrms.xml\"\n\n \n/include\n\n\n/menuContributionFile\n\n\n\n\nto \n\n\nmenuContributionFile\n\n\n/menuContributionFile\n\n\n\n\n\n\n\n\nWith this you can restart CAVE and will not see the MRMS menu anymore. Repeat this example for other product menus, such as \nlocal\n, \nhydro\n, \nscan\n, etc., to further customize D2D data menus for any level of localization.",
"text":"In the Localization Perspective you can navigate to D2D Volume Browser VbSources and click on volume.xml to expand. Then right-click on BASE and select Copy To... User (awips). You can then right-click again on the VbSources folder and select Refresh to see your new localization file called USER (awips) . Open the file and add or edit the model names: menuContributionFile \n include installTo=\"menu:models\" \n fileName=\"menus/volume/allFamilies.xml\" \n substitute key=\"modelName\" value=\"CMC\" / \n substitute key=\"menuName\" value=\"CMC\" / \n substitute key=\"frameCount\" value=\"41\" / \n substitute key=\"TP\" value=\"TP\"/ \n /include \n include installTo=\"menu:models\" \n fileName=\"menus/volume/allFamilies.xml\" \n substitute key=\"modelName\" value=\"DGEX\" / \n substitute key=\"menuName\" value=\"DGEX\" / \n substitute key=\"frameCount\" value=\"41\" / \n substitute key=\"TP\" value=\"TP\"/ \n /include \n ... Notice that you specify both the modelName (what it's named inside EDEX, such as NAM12), and menuName , if you prefer a more detailed menu entry, such as \"NAM 12km\". When you are finished, save the file and restart CAVE for the changes to take effect. Your new localization file exists on the EDEX server (assuming username awips) as /awips2/edex/data/utility/cave_static/users/awips/volumebrowser/VbSources/index.html and will exist on the local CAVE machine under ~/caveData/etc/user/awips/volumebrowser/VbSources/index.html",
"title":"Changing the models displayed with D2D bundles"
"text":"This example covers how to remove a menu (in this case MRMS ) from D2D: switch to the Localization Perspective find the mrms folder under CAVE Menus double-click to expand index.html right-click BASE and select Copy To... , then select USER level right-click refresh the mrms entry double click USER to open the editor and change menuContributionFile \n include installTo=\"menu:mrms?after=MRMS_MENU_START\"\n fileName=\"menus/mrms/mrms.xml\" \n /include /menuContributionFile to menuContributionFile /menuContributionFile With this you can restart CAVE and will not see the MRMS menu anymore. Repeat this example for other product menus, such as local , hydro , scan , etc., to further customize D2D data menus for any level of localization.",
"title":"Removing menus from the menubar"
},
{
"location":"/cave/cave-localization/",
"text":"Localization Preferences\n\uf0c1\n\n\nThe default localization site for Unidata AWIPS is BOU (Boulder, Colorado, where UCAR is located). When you are prompted to connect to an EDEX server, you can change the WFO ID as well. \n\n\n\n\nSince release 16.1.4, CAVE users can switch the localization site to any valid NWS WFO from \nCAVE \n Preferences \n Localization\n, where edits canbe made to both the site ID and EDEX server name. Click \nRestart\n after changes are applied. \n\n\n\n\nChange the site (example shows TBW Tampa Bay) and click \nOkay\n or \nApply\n and confirm the popup dialog, which informs you that you must \nrestart\n CAVE for the changes to take effect.",
"text":"The default localization site for Unidata AWIPS is BOU (Boulder, Colorado, where UCAR is located). When you are prompted to connect to an EDEX server, you can change the WFO ID as well. Since release 16.1.4, CAVE users can switch the localization site to any valid NWS WFO from CAVE Preferences Localization , where edits canbe made to both the site ID and EDEX server name. Click Restart after changes are applied. Change the site (example shows TBW Tampa Bay) and click Okay or Apply and confirm the popup dialog, which informs you that you must restart CAVE for the changes to take effect.",
"title":"Localization Preferences"
},
{
"location":"/install/start-edex/",
"text":"EDEX Service Manager\n\uf0c1\n\n\nThere are five EDEX service installed into \n/etc/init.d/\n, four of which run on boot:\n\n\nservice postgres start\nservice httpd-pypies start\nservice qpidd start\nservice edex_camel start\n\n\n\nThe fifth, \nedex_ldm\n, does \nnot run at boot\n to prevent filling up disk space if EDEX is not running. \n\n\nservice edex_ldm start\n\n\n\nAll of these services are started and stopped by a single program \nedex\n,\n\n\nedex start\n\uf0c1\n\n\nedex start\n\nStarting EDEX PostgreSQL: [ OK ]\nStarting httpd: [ OK ]\nStarting QPID [ OK ]\nStarting EDEX Camel (request): \nStarting EDEX Camel (ingest): \nStarting EDEX Camel (ingestGrib): \nStarting AWIPS LDM:The product-queue is OK.\n...\n\n\n\nedex stop\n\uf0c1\n\n\nedex stop\n\nStopping EDEX Camel (request): \nStopping EDEX Camel (ingest): \nStopping EDEX Camel (ingestGrib): \nStopping QPID [ OK ]\nStopping httpd: [ OK ]\nStopping EDEX PostgreSQL: [ OK ]\nStopping AWIPS LDM:Stopping the LDM server...\n...\n\n\n\nedex setup\n\uf0c1\n\n\nedex setup\n\n[edex] EDEX IP and Hostname Setup\n Checking /awips2/data/pg_hba.conf [OK]\n Checking /awips2/edex/bin/setup.env [OK]\n\n[edit] Hostname edex.unidata.ucar.edu added to /awips2/ldm/etc/ldmd.conf\n[done]\n\n\n\nThis command configures and/or confirms that the EDEX hostname and IP address definitions exist (\nedex setup\n is run by \nedex start\n).\n\n\n\n\nIf your EDEX server is running but you see the message \"Connectivity Error: Unable to validate localization preferences\"inCAVE,itmaymeanthatthedomainnamedefinedin\n/awips2/edex/bin/setup.env\ncannotberesolvedfrom\noutside\ntheserver.Somemachineshavedifferent\ninternally-resolved\nand\nexternally-resolved\ndomainnames(cloud-basedespecially).Thenamedefinedin\nsetup.env\nmustbe\nexternally-resolvable\n.\n\n\n\n\nedexlog\n\uf0c1\n\n\nedexlog\n\n[edex]EDEXLogViewer\n\n::Nologspecified-Defaultingtoingestlog\n::Viewing/awips2/edex/logs/edex-ingest-20151209.log.PressCTRL+Ctoexit\n\nINFO[Ingest.binlightning-1]/awips2/data_store/SFPA42_KWBC_091833_38031177.2015120918processedin:0.0050(sec)Latency:0.0550(sec)\nINFO[Ingest.obs-1]/awips2/data_store/metar/SAIN31_VABB_091830_131392869.2015120918processedin:0.0810(sec)Latency:0.1800(sec)\n\n\n\nMoreedexlogs...\n\n\nedexloggrib\nedexlogrequest\nedexlogldm\nedexlogradar\nedexlogsatellite\nedexlogtext\n\n\n\nedexusers\n\uf0c1\n\n\nToseealistofclientsconnectingtoyourEDEXserver,usethe\nedexusers[YYYYMMDD]\ncommand,where\nYYYYMMDD\nistheoptionaldatestring.\n\n\nedexusers\n\n--EDEXUsers20160826--\nuser@101.253.20.225\nuser@192.168.1.67\nawips@0.0.0.0\nawips@sdsmt.edu\n\n\n\nedexpurge\n\uf0c1\n\n\nToviewanystuckpurgejobsinPortgreSQL(ararebutseriousproblemifyourdiskfillsup).Thesolutiontothisistorun\nedexpurgereset\n.\n\n\n\n\nEDEXMemoryConfiguration\n\uf0c1\n\n\nThedirectory\n/awips2/edex/etc/\ncontainsfileswhichdefinetheamountofmemoryusedforeachofthethreeEDEXJVMs(ingest,ingestGrib,request):\n\n\nls-al/awips2/edex/etc/\n-rw-r--r--1awipsfxalpha1501Dec700:37default.sh\n-rw-r--r--1awipsfxalpha1655Dec1219:47ingestGrib.sh\n-rw-r--r--1awipsfxalpha937Dec1219:46ingest.sh\n-rw-r--r--1awipsfxalpha1231Dec1219:47request.sh\n\n\n\nEachfilecontainsthe\nXmx\ndefinitionformaximummemory:\n\n\nexportINIT_MEM=512#inMeg\nexportMAX_MEM=4096#inMeg\n\n\n\nAftereditingthesefiles,youmustrestartedex(\nserviceedex_camelrestart\n).\n\n\n\n\nEDEXPluginConfiguration\n\uf0c1\n\n\nThedirectory\n/awips2/edex/conf/modes\ncontainsXMLfileswithrulesdefiningwhichpluginsareincludedorexcludedwitheachJVM(ingest,ingestGrid,request):\n\n
"text":"There are five EDEX service installed into /etc/init.d/ , four of which run on boot: service postgres start\nservice httpd-pypies start\nservice qpidd start\nservice edex_camel start The fifth, edex_ldm , does not run at boot to prevent filling up disk space if EDEX is not running. service edex_ldm start All of these services are started and stopped by a single program edex ,",
"title":"EDEX Service Manager"
},
{
"location":"/install/start-edex/#edex-start",
"text":"edex start\n\nStarting EDEX PostgreSQL: [ OK ]\nStarting httpd: [ OK ]\nStarting QPID [ OK ]\nStarting EDEX Camel (request): \nStarting EDEX Camel (ingest): \nStarting EDEX Camel (ingestGrib): \nStarting AWIPS LDM:The product-queue is OK.\n...",
"title":"edex start"
},
{
"location":"/install/start-edex/#edex-stop",
"text":"edex stop\n\nStopping EDEX Camel (request): \nStopping EDEX Camel (ingest): \nStopping EDEX Camel (ingestGrib): \nStopping QPID [ OK ]\nStopping httpd: [ OK ]\nStopping EDEX PostgreSQL: [ OK ]\nStopping AWIPS LDM:Stopping the LDM server...\n...",
"title":"edex stop"
},
{
"location":"/install/start-edex/#edex-setup",
"text":"edex setup\n\n[edex] EDEX IP and Hostname Setup\n Checking /awips2/data/pg_hba.conf [OK]\n Checking /awips2/edex/bin/setup.env [OK]\n\n[edit] Hostname edex.unidata.ucar.edu added to /awips2/ldm/etc/ldmd.conf\n[done] This command configures and/or confirms that the EDEX hostname and IP address definitions exist ( edex setup is run by edex start ). If your EDEX server is running but you see the message \"Connectivity Error: Unable to validate localization preferences\" in CAVE, it may mean that the domain name defined in /awips2/edex/bin/setup.env can not be resolved from outside the server. Some machines have different internally-resolved and externally-resolved domain names (cloud-based especially). The name defined in setup.env must be externally-resolvable .",
"text":"To see a list of clients connecting to your EDEX server, use the edex users [YYYYMMDD] command, where YYYYMMDD is the optional date string. edex users\n\n -- EDEX Users 20160826 --\nuser@101.253.20.225\nuser@192.168.1.67\nawips@0.0.0.0\nawips@sdsmt.edu",
"title":"edex users"
},
{
"location":"/install/start-edex/#edex-purge",
"text":"To view any stuck purge jobs in PortgreSQL (a rare but serious problem if your disk fills up). The solution to this is to run edex purge reset .",
"text":"The directory /awips2/edex/etc/ contains files which define the amount of memory used for each of the three EDEX JVMs (ingest, ingestGrib, request): ls -al /awips2/edex/etc/\n-rw-r--r-- 1 awips fxalpha 1501 Dec 7 00:37 default.sh\n-rw-r--r-- 1 awips fxalpha 1655 Dec 12 19:47 ingestGrib.sh\n-rw-r--r-- 1 awips fxalpha 937 Dec 12 19:46 ingest.sh\n-rw-r--r-- 1 awips fxalpha 1231 Dec 12 19:47 request.sh Each file contains the Xmx definition for maximum memory: export INIT_MEM=512 # in Meg\nexport MAX_MEM=4096 # in Meg After editing these files, you must restart edex ( service edex_camel restart ).",
"text":"The directory /awips2/edex/conf/modes contains XML files with rules defining which plugins are included or excluded with each JVM (ingest, ingestGrid, request): ls -la /awips2/edex/conf/modes\n-rw-r--r-- 1 awips fxalpha 1982 Dec 6 21:26 grid-modes.xml\n-rw-r--r-- 1 awips fxalpha 928 Dec 6 21:24 ingest-modes.xml\n-rw-r--r-- 1 awips fxalpha 1689 Dec 6 21:24 request-modes.xml EDEX services are all registered through spring. By including or excluding specific spring files we can determine at startup which services the EDEX instance should start. All mode files are merged at startup. Modes files with modes that have the same name are combined so the end result is an aggregate of patterns in all files. Include and exclude tags should have regular expressions that are compatible with Java's Pattern class. If you provide no include tag for a particular mode, the include defaults to .* . An example of /awips2/edex/conf/modes/ingest-modes.xml , with a number of unused plugin decoders excluded because the data are not available outside of the SBN: ?xml version=\"1.0\" encoding=\"UTF-8\" standalone=\"yes\"? edexModes \n mode name=\"ingest\" \n exclude .*request.* /exclude \n exclude edex-security.xml /exclude \n exclude rpgenvdata.* /exclude \n exclude taf.* /exclude \n exclude ldad.* /exclude \n exclude ghcd.* /exclude \n exclude geomag.* /exclude \n exclude mping.* /exclude \n exclude modis.* /exclude \n exclude mosaic.* /exclude \n exclude shef.* /exclude \n exclude madis.* /exclude \n exclude idft.* /exclude \n exclude ffmp.* /exclude \n exclude stormtrack.* /exclude \n exclude solarimage.* /exclude \n exclude retrieval.* /exclude \n exclude regionalsat.* /exclude \n exclude pointset-netcdf.* /exclude \n exclude ncscat.* /exclude \n exclude profiler.* /exclude \n exclude bufrobs.* /exclude \n exclude bufrmthdw.* /exclude \n exclude sgwh.* /exclude \n /mode /edexModes",
"title":"EDEX Plugin Configuration"
},
{
"location":"/edex/ldm/",
"text":"Default LDM Feeds for EDEX\n\uf0c1\n\n\nfrom \n/awips2/ldm/etc/ldmd.conf\n\n\nREQUEST NEXRAD3 \"./p(DHR|DPR|DSP|DTA|DAA|DVL|EET|HHC|N0Q|N0S|N0U|OHA|NVW|NTV|NST).\" idd.unidata.ucar.edu\nREQUEST FNEXRAD|IDS|DDPLUS|UNIWISC \".*\" idd.unidata.ucar.edu\nREQUEST NGRID \".*\" idd.unidata.ucar.edu\nREQUEST NOTHER \"^TIP... KNES.*\" idd.unidata.ucar.edu\nREQUEST HDS|NIMAGE \".*\" idd.unidata.ucar.edu\n\nREQUEST CONDUIT \"nam\" idd.unidata.ucar.edu\nREQUEST CONDUIT \"rap\" idd.unidata.ucar.edu\nREQUEST CONDUIT \"pgrb2\" idd.unidata.ucar.edu\nREQUEST CONDUIT \"nwstg\" idd.unidata.ucar.edu\n\n\n\n\n\nRemember than LDM commands such as these require \nTAB SEPARATION\n between items.\n\n\n\n\nOptional LDM Feeds\n\uf0c1\n\n\nFNMOC and CMC models\n\n\nREQUEST FNMOC \".*\" idd.unidata.ucar.edu\nREQUEST CMC \".*\" idd.unidata.ucar.edu\n\n\n\nLightning (restricted to educational use with rebroadcasting restricted)\n\n\nREQUEST LIGHTNING \".*\" striker2.atmos.albany.edu\nREQUEST LIGHTNING \".*\" idd.unidata.ucar.edu\n\n\n\nFSL/GSD Experimental HRRR (Sub-hourly)\n\n\nREQUEST FSL2 \"^GRIB2.FSL.HRRR\" hrrr.unidata.ucar.edu\n\n\n\nRestart the LDM\n\uf0c1\n\n\nsudo service edex_ldm restart\n\nldmadmin restart\n\n\n\nMonitor Incoming Data Feeds\n\uf0c1\n\n\nTo watch incoming data in real-time:\n\n\nnotifyme -vl -\n\n\n\nTo watch for a specific product and feed and time (360 sec = 6 min):\n\n\nnotifyme -vl - -h localhost -f NEXRAD3 -p DHR -o 360\n\n\n\nTo watch the same on a remote queue:\n\n\nnotifyme -vl - -h idd.unidata.ucar.edu -f NEXRAD3 -p DHR -o 360\n\n\n\nLDM Logging\n\uf0c1\n\n\nedex log ldm\n\n[edex] EDEX Log Viewer\n\n :: Viewing /awips2/ldm/logs/ldmd.log. Press CTRL+C to exit\n\nAug 26 15:05:10 edextest pqact[5811] NOTE: Filed in \"/awips2/data_store/grid/HRRR/HRRR_CONUS_2p5km_201608262000_F006_MXUPHL01-21387192.grib2\": 406227 20160826210510.477 NGRID 21387192 YZCG86 KWBY 262000 !grib2/ncep/HRRR/#255/201608262000F006/MXUPHL01/5000-2000 m HGHT\nAug 26 15:05:11 edextest edexBridge[5812] NOTE: Sent 2 messages (0 at the end of the queue, 2 normally).\nAug 26 15:05:11 edextest pqact[5811] NOTE: Filed in \"/awips2/data_store/grid/HRRR/HRRR_CONUS_2p5km_201608262000_F006_CICEP-21387200.grib2\": 369464 20160826210511.484 NGRID 21387200 YMCG98 KWBY 262000 !grib2/ncep/HRRR/#255/201608262000F006/CICEP/0 - NONE\nAug 26 15:05:12 edextest edexBridge[5812] NOTE: Sent 9 messages (0 at the end of the queue, 9 normally).\nAug 26 15:05:12 edextest pqact[5811] NOTE: Filed in \"/awips2/data_store/grid/HRRR/HRRR_CONUS_2p5km_201608262000_F006_LTNG-21387205.grib2\": 482800 20160826210512.254 NGRID 21387205 YZCG98 KWBY 262000 !grib2/ncep/HRRR/#255/201608262000F006/LTNG/0 - EATM\nAug 26 15:05:13 edextest edexBridge[5812] NOTE: Sent 1 messages (0 at the end of the queue, 1 normally).\nAug 26 15:05:13 edextest pngg2gini[22317] NOTE: Starting Up\nAug 26 15:05:13 edextest pngg2gini[22317] INFO: output file pathname: /awips2/data_store/ingest/nexrcomp_4km_2105_20160826_ntp_0.rad\nAug 26 15:05:13 edextest pngg2gini[22317] NOTE: unPNG:: 117632 888533 7.5535\nAug 26 15:05:13 edextest pngg2gini[22317] NOTE: Exiting\nAug 26 15:05:14 edextest edexBridge[5812] NOTE: Sent 17 messages (0 at the end of the queue, 17 normally).",
"text":"To watch incoming data in real-time: notifyme -vl - To watch for a specific product and feed and time (360 sec = 6 min): notifyme -vl - -h localhost -f NEXRAD3 -p DHR -o 360 To watch the same on a remote queue: notifyme -vl - -h idd.unidata.ucar.edu -f NEXRAD3 -p DHR -o 360",
"title":"Monitor Incoming Data Feeds"
},
{
"location":"/edex/ldm/#ldm-logging",
"text":"edex log ldm\n\n[edex] EDEX Log Viewer\n\n :: Viewing /awips2/ldm/logs/ldmd.log. Press CTRL+C to exit\n\nAug 26 15:05:10 edextest pqact[5811] NOTE: Filed in \"/awips2/data_store/grid/HRRR/HRRR_CONUS_2p5km_201608262000_F006_MXUPHL01-21387192.grib2\": 406227 20160826210510.477 NGRID 21387192 YZCG86 KWBY 262000 !grib2/ncep/HRRR/#255/201608262000F006/MXUPHL01/5000-2000 m HGHT\nAug 26 15:05:11 edextest edexBridge[5812] NOTE: Sent 2 messages (0 at the end of the queue, 2 normally).\nAug 26 15:05:11 edextest pqact[5811] NOTE: Filed in \"/awips2/data_store/grid/HRRR/HRRR_CONUS_2p5km_201608262000_F006_CICEP-21387200.grib2\": 369464 20160826210511.484 NGRID 21387200 YMCG98 KWBY 262000 !grib2/ncep/HRRR/#255/201608262000F006/CICEP/0 - NONE\nAug 26 15:05:12 edextest edexBridge[5812] NOTE: Sent 9 messages (0 at the end of the queue, 9 normally).\nAug 26 15:05:12 edextest pqact[5811] NOTE: Filed in \"/awips2/data_store/grid/HRRR/HRRR_CONUS_2p5km_201608262000_F006_LTNG-21387205.grib2\": 482800 20160826210512.254 NGRID 21387205 YZCG98 KWBY 262000 !grib2/ncep/HRRR/#255/201608262000F006/LTNG/0 - EATM\nAug 26 15:05:13 edextest edexBridge[5812] NOTE: Sent 1 messages (0 at the end of the queue, 1 normally).\nAug 26 15:05:13 edextest pngg2gini[22317] NOTE: Starting Up\nAug 26 15:05:13 edextest pngg2gini[22317] INFO: output file pathname: /awips2/data_store/ingest/nexrcomp_4km_2105_20160826_ntp_0.rad\nAug 26 15:05:13 edextest pngg2gini[22317] NOTE: unPNG:: 117632 888533 7.5535\nAug 26 15:05:13 edextest pngg2gini[22317] NOTE: Exiting\nAug 26 15:05:14 edextest edexBridge[5812] NOTE: Sent 17 messages (0 at the end of the queue, 17 normally).",
"title":"LDM Logging"
},
{
"location":"/edex/data-distribution-files/",
"text":"EDEX alerts the appropriate decoding plug-ins of new data by use of XML files that describe data based on regular expressions. If the WMO header, or file name, matches a regular expression listed in a distribution XML, then EDEX will put a message into the QPID queue for the decoder which indicates that a piece of data is available. If a piece of data does not match any distribution XML, EDEX will:\n\n\n\n\n\n\nCreate an entry in \n/awips2/edex/logs/edex-ingest-unrecognized-files-yyyymmdd.log\n\n\n\n\n\n\nSkip processing of the unrecognized file.\n\n\n\n\n\n\nDistribution filters are stored in the \nedex_static\n branch of the Localization Store, and a list of available files can be found in the base-level directory. \n\n\nFor each plug-in, the distribution file is named \ndata-type\n.xml\n; for example, the distribution file for satellite data is \nsatellite.xml\n. The distribution files follow the AWIPS base/site localization pattern: \n\n\n[root@edex]# cd /awips2/edex/data/utility/edex_static/base/distribution\n[root@edex distribution]# ls\nacars.xml ffg.xml poessounding.xml\nairep.xml goessounding.xml profiler.xml\nairmet.xml grib.xml q2.xml\natcf.xml hpe.xml radar.xml\naww.xml idft.xml recco.xml\nbinlightning.xml intlsigmet.xml redbook.xml\nbufrascat.xml ldadhydro.xml satellite.mcidas.xml\nbufrhdw.xml ldadmanual.xml satellite.xml\nbufrmos.xml ldadmesonet.xml sfcobs.xml\nbufrmthdw.xml ldadprofiler.xml shef.xml\nbufrncwf.xml loctables.xml svrwx.xml\nbufrquikscat.xml lsr.xml taf.xml\nbufrsgwhv.xml mcidas.xml tcg.xml\nbufrsgwh.xml modelsounding.xml tcm.xml\nbufrsigwx.xml mosaic.xml tcs.xml\nbufrssha.xml ncccfp.xml textlightning.xml\nbufrssmi.xml ncgrib.xml text.xml\nbufrua.xml ncscat.xml uair.xml\nccfp.xml nctext.xml vaa.xml\nconvsigmet.xml nonconvsigmet.xml warning.xml\ncwa.xml obs.xml wcp.xml\ndhr.xml pafm.xml\ndpa.xml pirep.xml\n\n\n\n\n\n\n\nbase files are located in \n/awips2/edex/data/utility/edex_static/base/distribution \n\n\n\n\n\n\nsite override distribution files are located in \n/awips2/edex/data/utility/edex_static/site/XXX/distribution\n, where \nXXX\n is the site identifier.\n\n\n\n\n\n\nNote that site-level files override the base files; as a result, local modifications to distribution files must be made as follows:\n\n\n\n\n\n\nThe base distribution file must be copied from \n/awips2/edex/data/utility/edex_static/base/distribution\n to \n/awips2/edex/data/utility/edex_static/site/XXX/distribution\n\n\n\n\n\n\nThe local modification must be made to the file in \n/awips2/edex/data/utility/edex_static/site/XXX/distribution\n\n\n\n\n\n\nThe basic structure of the distribution file is:\n\n\nrequestPatterns xmlns:ns2=\"group\"\n\n \nregex\npattern\n/regex\n\n \nregex\npattern\n/regex\n\n\n/requestPatterns\n\n\n\n\nIn each \n \ntag, \npattern\n is replaced with a regular expression that will match either the filename or the WMO header of the raw data. Only data that matches a pattern in the distribution file will be processed.\n\n\nThe contents of the base version of the radar distribution file:\n\n\n[root@edex]# cd /awips2/edex/data/utility/edex_static/base/distribution/\n[root@edex]# tail -4 radar.xml\n\n\nrequestPatterns xmlns:ns2=\"group\"\n\n\nregex\n^SDUS[234578]..*\n/regex\n\n\nregex\n^RadarServer.*\n/regex\n\n\n/requestPatterns\n\n\n\n\nLookingatthebaseradar.xmldistributionfileinthepreviousexample,therearetworegularexpressions.ThefirstregularexpressionmatchesthestandardWMOIDofradarproducts.ViatheedexBridgetheLDMwillplaceamessageintheexternal.dropboxQPIDqueue,indicatingaradarproducthasarrived.EDEXwillthentakethemessagecontainingtheradarWMOIDandcompareitagainsttheregularexpressionsinradar.xml.Ifamatchisfound,EDEXp
"text":"As a quick example, suppose we have a local data source for satellite imagery that does not have a WMO header; also suppose that the data source writes to files whose names start with LOCAL.sat . To add this locally produced satellite data file to the EDEX distribution; perform the following steps. Copy the base version of satellite.gini.xml from the base distribution directory /awips2/edex/data/utility/edex_static/base/distribution into the site distribution directory /awips2/edex/data/utility/edex_static/site/XXX/distribution Edit the site version of satellite.xml , adding a new regex /regex tag immediately below the existing regular expression ( regex /regex ) tag. The contents of the tag will be LOCAL.sat . The final result will be: requestPatterns xmlns:ns2=\"group\" \n regex TI[CGT]... .... /regex \n regex .*NEXRCOMP.* /regex \n regex ^LOCAL.sat.* /regex /requestPatterns Save the file and exit the editor. EDEX will automatically pick up the new distribution pattern. Raw files are written to /data_store , and a message is sent via QPID to the EDEX distribution service from the LDM. When a regular expression match is found in a data distribution file, the raw data file is placed in a queue for the matching plugin to decode and process. The distribution files are used to match file headers as well as filenames, which is how files dropped into EDEX's manual endpoint ( /awips2/data_store/ingest ) are processed.",
"title":"Adding a REGEX to the Satellite Data Distribution File"
"text":"Because these files are in the edex_static/ directory, they have to be manually edited using a text editor. You should not edit the base files; rather, you should copy the base version to your site and then edit the site version. The regular expressions in the distribution files need to correspond with the regular expressions in the LDM pqact.conf file. If patterns exist in pqact.conf but are not in the distribution files, then raw data files will be written to /data_store but will not be ingested and processed by EDEX. Entries for these non-ingested files would be written to the unrecognized files log in /awips/edex/logs .",
"text":"/awips2/edex/data/utility/edex_static/base/distribution/obs.xml Processes any file header that starts with SA or SP , which should match any WMO header that contains METAR data (e.g. SAUS , SPUS , SACN , SAMX ). requestPatterns xmlns:ns2=\"group\" \n regex ^S[AP].* /regex /requestPatterns",
"text":"/awips2/edex/data/utility/edex_static/base/distribution/text.xml Processes lots of WM patterns. The second pattern ^S[A-CEG-Z].* matches any header that starts with S except for SD or SF , so it also matches the SA and SP files that the obs.xml plugin matches. This means that METARs are processed by both plugins simultaneously. requestPatterns \n regex ^[ACFNRUW][A-Z].* /regex \n regex ^S[ACEG-Z].* /regex \n regex ^T[BCX].* /regex \n regex ^SF[A-OQ-TVZ].* /regex \n regex ^SDUS1.* /regex \n regex ^SDUS4[1-6].* /regex \n regex ^SDUS9[^7].* /regex \n regex ^SFU[^S].* /regex \n regex ^SFUS4[^1].* /regex \n regex ^SFP[^A].* /regex \n regex ^SFPA[^4].* /regex \n regex ^SFPA4[^1].* /regex \n regex ^BMBB91.* /regex \n regex ^N.* /regex \n regex ^F[EHIJKLMQVWX].* /regex /requestPatterns",
"text":"/awips2/edex/data/utility/edex_static/base/distribution/grib.xml The grib/grid decoder distribution file matches all numerical grids distributed over the IDD NGRID feed by matching WMO header, and from CONDUIT by matching the .grib file extension. requestPatterns \n !-- Super Set of all possible WMO grib patterns -- \n regex ^[EHLMOYZ][A-Z]{3}\\d{2} /regex \n !-- This to match Unidata CONDUIT products w/o standard headers -- \n regex .*grib.* /regex \n regex ^US058.* /regex \n regex ^CMC_reg.* /regex /requestPatterns Important notes about regular expressions: Any time a new entry is placed in the pqact.conf file on LDM, a corresponding entry needs to be added to the appropriate Data Distribution file in the data distribution directory, or the data file will be logged to edex-ingest-unrecognized-files-YYYYMMDD.log Any time an entry is removed from the pqact.conf file, the corresponding entry should be removed from the appropriate Data Distribution file in the data distribution directory.",
"title":"Grib Data"
},
{
"location":"/edex/new-grid/",
"text":"UnrecognizedgridscanbedecodedbyEDEXsimplybydropping\n*.grib\nor\n*.grib2\nfilesinto\n/awips2/data_store/ingest/\n\n\nToaddsupportforanewgrid,twoeditsmustbemade:\n\n\n\n\nGeospatialprojection\nmustbedefinedina\ngridnavigationfile\n\n\nGridname\n,\ncenter\n,\nsubcenter\n,and\nprocessID\nmustbedefinedina\nmodeldefinitionfile\n.\n\n\n\n\nIngestanUnsupportedGrid\n\uf0c1\n\n\n\n\n\n\nDownloadanexamplegrib1fileandrenametoa\n*.grib\nextension,thencopytothemanualingestpoint\n/awips2/data_store/ingest/\n\n\n\nwgethttp://www.unidata.ucar.edu/staff/mjames/14102318_nmm_d01.GrbF00600 -O wrf.grib\n\ncp wrf.grib /awips2/data_store/ingest/\n\n\n\nRemember that the data distribution file (\n/awips2/edex/data/utility/edex_static/base/distribution/grib.xml\n) will match filename which have the \n*.grib\n extension.\n\n\n\n\n\n\nConfirm that the grib file decodes in the grib log file:\n\n\nedex log grib\n\nINFO [Ingest.GribDecode] /awips2/data_store/ingest/grib/20141026/14/wrf.grib processed in: 0.1200 (sec) Latency: 21.8080 (sec)\nINFO [Ingest.GribDecode] /awips2/data_store/ingest/grib/20141026/14/wrf.grib processed in: 0.1180 (sec) Latency: 21.8140 (sec)\nINFO [Ingest.GribDecode] /awips2/data_store/ingest/grib/20141026/14/wrf.grib processed in: 0.4230 (sec) Latency: 21.8360 (sec)\nINFO [Ingest.GribDecode] /awips2/data_store/ingest/grib/20141026/14/wrf.grib processed in: 0.2240 (sec) Latency: 21.9140 (sec)\n\n...\n\n\n\n\n\n\n\nCheck that the hdf5 data directory exists for our unnamed grid\n\n\nls -latr /awips2/edex/data/hdf5/grid/GribModel:7:0:89\n\n\n\nThough the grib file has been decoded, it has been given a generic name with its center, subcenter, and process IDs (7, 0, 89, respectively). \n\n\n\n\n\n\nDetermine Grid Projection\n\uf0c1\n\n\nWhen the grid was ingested a record was added to the \ngrid_coverage\n table with its navigation information:\n\n\npsql metadata\n\nmetadata=# select nx,ny,dx,dy,majoraxis,minoraxis,la1,lo1,lov,latin1,latin2 from gridcoverage where id=(select distinct(location_id) from grid_info where datasetid='GribModel:7:0:89');\n nx | ny | dx | dy | majoraxis | minoraxis | la1 | lo1 | lov | latin1 | latin2 \n-----+-----+------------------+------------------+-----------+-----------+------------------+-------------------+-------------------+------------------+------------------\n 201 | 155 | 4.29699993133545 | 4.29699993133545 | 6378160 | 6356775 | 42.2830009460449 | -72.3610000610352 | -67.0770034790039 | 45.3680000305176 | 45.3680000305176\n(1 row)\n\n\n\nCompare with the projection info returned by wgrib on the original file:\n\n\nwgrib -V wrf.grib\n\nrec 799:27785754:date 2014102318 ALBDO kpds5=84 kpds6=1 kpds7=0 levels=(0,0) grid=255 sfc 6hr fcst: bitmap: 736 undef\n ALBDO=Albedo [%]\n timerange 0 P1 6 P2 0 TimeU 1 nx 201 ny 155 GDS grid 3 num_in_ave 0 missing 0\n center 7 subcenter 0 process 89 Table 2 scan: WE:SN winds(grid) \n Lambert Conf: Lat1 42.283000 Lon1 -72.361000 Lov -67.077000\n Latin1 45.368000 Latin2 45.368000 LatSP 0.000000 LonSP 0.000000\n North Pole (201 x 155) Dx 4.297000 Dy 4.297000 scan 64 mode 8\n min/max data 5 21.9 num bits 8 BDS_Ref 50 DecScale 1 BinScale 0\n\n\n\nNotice that our grib1 file is a \nLambert Conformal\n projection. We will need these values for the next step. Note that \nthere is a tolerance of +/- 0.1 degrees\n to keep in mind when defining your coverage area.\n\n\nCreate Grid Projection File\n\uf0c1\n\n\nGrid projection files are stored in \n/awips2/edex/data/utility/edex_static/base/grib/grids/\n and there are four grid coverage types available:\n\n\n\n\n\n\nlambertConformalGridCoverage\n example\n\n\nlambertConformalGridCoverage\n\n \nname\n305\n/name\n\n \ndescription\nRegional - CONUS (Lambert Conformal)\n/description\n\n \nla1\n16.322\n/la1\n\n \nlo1\n-125.955\n/lo1\n\n \nfirstGridPointCorner\nLowerLeft\n/firstGridPointCorner\n\n \nnx\n151\n/
"text":"Download an example grib1 file and rename to a *.grib extension, then copy to the manual ingest point /awips2/data_store/ingest/ wget http://www.unidata.ucar.edu/staff/mjames/14102318_nmm_d01.GrbF00600 -O wrf.grib\n\ncp wrf.grib /awips2/data_store/ingest/ Remember that the data distribution file ( /awips2/edex/data/utility/edex_static/base/distribution/grib.xml ) will match filename which have the *.grib extension. Confirm that the grib file decodes in the grib log file: edex log grib\n\nINFO [Ingest.GribDecode] /awips2/data_store/ingest/grib/20141026/14/wrf.grib processed in: 0.1200 (sec) Latency: 21.8080 (sec)\nINFO [Ingest.GribDecode] /awips2/data_store/ingest/grib/20141026/14/wrf.grib processed in: 0.1180 (sec) Latency: 21.8140 (sec)\nINFO [Ingest.GribDecode] /awips2/data_store/ingest/grib/20141026/14/wrf.grib processed in: 0.4230 (sec) Latency: 21.8360 (sec)\nINFO [Ingest.GribDecode] /awips2/data_store/ingest/grib/20141026/14/wrf.grib processed in: 0.2240 (sec) Latency: 21.9140 (sec)\n\n... Check that the hdf5 data directory exists for our unnamed grid ls -latr /awips2/edex/data/hdf5/grid/GribModel:7:0:89 Though the grib file has been decoded, it has been given a generic name with its center, subcenter, and process IDs (7, 0, 89, respectively).",
"text":"When the grid was ingested a record was added to the grid_coverage table with its navigation information: psql metadata\n\nmetadata=# select nx,ny,dx,dy,majoraxis,minoraxis,la1,lo1,lov,latin1,latin2 from gridcoverage where id=(select distinct(location_id) from grid_info where datasetid='GribModel:7:0:89');\n nx | ny | dx | dy | majoraxis | minoraxis | la1 | lo1 | lov | latin1 | latin2 \n-----+-----+------------------+------------------+-----------+-----------+------------------+-------------------+-------------------+------------------+------------------\n 201 | 155 | 4.29699993133545 | 4.29699993133545 | 6378160 | 6356775 | 42.2830009460449 | -72.3610000610352 | -67.0770034790039 | 45.3680000305176 | 45.3680000305176\n(1 row) Compare with the projection info returned by wgrib on the original file: wgrib -V wrf.grib\n\nrec 799:27785754:date 2014102318 ALBDO kpds5=84 kpds6=1 kpds7=0 levels=(0,0) grid=255 sfc 6hr fcst: bitmap: 736 undef\n ALBDO=Albedo [%]\n timerange 0 P1 6 P2 0 TimeU 1 nx 201 ny 155 GDS grid 3 num_in_ave 0 missing 0\n center 7 subcenter 0 process 89 Table 2 scan: WE:SN winds(grid) \n Lambert Conf: Lat1 42.283000 Lon1 -72.361000 Lov -67.077000\n Latin1 45.368000 Latin2 45.368000 LatSP 0.000000 LonSP 0.000000\n North Pole (201 x 155) Dx 4.297000 Dy 4.297000 scan 64 mode 8\n min/max data 5 21.9 num bits 8 BDS_Ref 50 DecScale 1 BinScale 0 Notice that our grib1 file is a Lambert Conformal projection. We will need these values for the next step. Note that there is a tolerance of +/- 0.1 degrees to keep in mind when defining your coverage area.",
"text":"Model definition XML files are found in /awips2/edex/data/utility/edex_static/base/grid/models/ . Since our grib1 file has a center ID of 7 (NCEP) we will edit the gribModels_NCEP-7.xml file. cd /awips2/edex/data/utility/edex_static/base/grib/models/\n\nvi gribModels_NCEP-7.xml in gribModelSet add an entry model \n name WRF /name \n center 7 /center \n subcenter 0 /subcenter \n grid 201155 /grid \n process \n id 89 /id \n /process \n /model save the file and restart EDEX for the changes to take effect. sudo service edex_camel restart Now copy the wrf.grib file again to /awips2/data_store/ingest/ . If everything is correct we will not see any persistence errors since the grid is now named WRF and not GribModel:7:0:89 . cp wrd.grib /awips2/data_store/ingest/\n\nedex log grib After you have confirmed that the grid was ingested with the given name, you can edit the D2D product menus to display the new grid .",
"text":"If you ingest a piece of data and the parameter appears as unknown in the metadata database, ensure that the correct parameter tables are in place for the center/subcenter. Make sure the latitude and longitude entries in your coverage specification file match those of your ingested raw grib file. There is a tolerance of +/- 0.1 degree to keep in mind when defining your coverage area. If some of the information is unknown, using a grib utility application such as wgrib and wgrib2 (not delivered) can be useful in determining the information that must be added to correctly process a new grib file.",
"text":"AWIPS uses a plugin-based purge strategy for HDF5 data, allowing the user to change the purge frequency for each plugin individually, and specific products for a particular plugin.\n\n\n\n\nPurge is triggered by a quartz timer event that fires at 30 minutes after each hour. \n\n\n\n\nPurging rules are defined in XML files in the Localization Store, accessible from the CAVE localization perspective. On EDEX, most are located in \n/awips2/edex/data/utility/common_static/base/purge\n, and follow the \nbase/site\n localization pattern (e.g. site purge files are in \nsite/XXX/purge\n rather than \nbase/purge\n, where XXX is the site identifier.\n\n\nTime-base purge\n\uf0c1\n\n\nIf a plugin has no XML file, the default rule of 1 day (24 hours) is used, from \n/awips2/edex/data/utility/common_static/base/purge/defaultPurgeRules.xml\n \n\n\npurgeRuleSet\n\n \ndefaultRule\n\n \nperiod\n01-00:00:00\n/period\n\n \n/defaultRule\n\n\n/purgeRuleSet\n\n\n\n\nTime-based purging uses the \nreference time\n of the data, and dtermination of the reference time is decoder based. \n\n\n30-day NEXRAD3 Example\n\uf0c1\n\n\nModify \n/awips2/edex/data/utility/common_static/base/purge/radarPurgeRules.xml\n to increase the data retention period from 7 to 31 days:\n\n\npurgeRuleSet\n\n \ndefaultRule\n\n \nperiod\n31-00:00:00\n/period\n\n \n/defaultRule\n\n\n/purgeRuleSet\n\n\n\n\nNote\n: you do NOT have to restart EDEX when you change a purge rule!\n\n\nFrame-based purge\n\uf0c1\n\n\nSome plugins use frame-base purging, retaining and certain number of prpduct \"versions\". \n\n\n/awips2/edex/data/utility/common_static/base/purge/satellitePurgeRules.xml\n\n\npurgeRuleSet\n\n \nkey\nsectorID\n/key\n\n \nkey\nphysicalElement\n/key\n\n \ndefaultRule\n\n \nversionsToKeep\n196\n/versionsToKeep\n\n \n/defaultRule\n\n \nrule\n\n \nkeyValue\nNEXRCOMP\n/keyValue\n\n \nversionsToKeep\n288\n/versionsToKeep\n\n \n/rule\n\n \nrule\n\n \nkeyValue\nAlaska National\n/keyValue\n\n \nversionsToKeep\n48\n/versionsToKeep\n\n \n/rule\n\n\n\n\n\n\nIn the above example, notice a \ndefault rule\n (196) as well as specific sectors with their own rules. \n\n\n\n\nPurge Logs\n\uf0c1\n\n\nData purge events are logged to the file \nedex-ingest-purge-\nyyyymmdd\n.log\n, where \nyyyymmdd\n is the date stamp. \n\n\ntail -f edex-ingest-purge-20120327.log\n\n--------START LOG PURGE---------\nINFO 2012-03-27 00:30:00,027 [DefaultQuartzScheduler_Worker-3] PurgeLogger: EDEX - PURGE LOGS::Skipped file with invalid fileName: afos-trigger.log\nINFO 2012-03-27 00:30:00,193 [DefaultQuartzScheduler_Worker-3] PurgeLogger: EDEX - PURGE LOGS::Removed 1 old files\nINFO 2012-03-27 00:31:23,155 [DefaultQuartzScheduler_Worker-3] PurgeLogger: EDEX - PURGE LOGS::Archived 14 files\nINFO 2012-03-27 00:31:23,155 [DefaultQuartzScheduler_Worker-3] PurgeLogger: EDEX - PURGE LOGS::Skipped processing 1 files\nINFO 2012-03-27 00:31:23,155 [DefaultQuartzScheduler_Worker-3] PurgeLogger: EDEX - PURGE LOGS::---------END LOG PURGE-----------\n\n\n\nAll Purge Rules\n\uf0c1\n\n\nTo see all purge rule directories (base, site, region, configured):\n\n\nfind /awips2/edex/data/utility -name purge\n\n/awips2/edex/data/utility/edex_static/region/CR/purge\n/awips2/edex/data/utility/edex_static/base/purge\n/awips2/edex/data/utility/edex_static/configured/OAX/purge\n/awips2/edex/data/utility/edex_static/site/OAX/purge\n/awips2/edex/data/utility/common_static/region/CR/purge\n/awips2/edex/data/utility/common_static/base/purge\n/awips2/edex/data/utility/common_static/configured/OAX/purge\n/awips2/edex/data/utility/common_static/site/AFC/purge\n/awips2/edex/data/utility/common_static/site/OAX/purge\n\n\n\nTo see a list of the data plug-ins that have purge rules:\n\n\nfind /awips2/edex/data/utility -name \"*PurgeRules.xml\"\n\n/awips2/edex/data/utility/edex_static/base/purge/airmetPurgeRules.xml\n/awips2/edex/data/utility/edex_static/base/purge/convsigmetPurgeRules.xml\n/awips2/edex/d
"text":"If a plugin has no XML file, the default rule of 1 day (24 hours) is used, from /awips2/edex/data/utility/common_static/base/purge/defaultPurgeRules.xml purgeRuleSet \n defaultRule \n period 01-00:00:00 /period \n /defaultRule /purgeRuleSet Time-based purging uses the reference time of the data, and dtermination of the reference time is decoder based.",
"text":"Modify /awips2/edex/data/utility/common_static/base/purge/radarPurgeRules.xml to increase the data retention period from 7 to 31 days: purgeRuleSet \n defaultRule \n period 31-00:00:00 /period \n /defaultRule /purgeRuleSet Note : you do NOT have to restart EDEX when you change a purge rule!",
"title":"30-day NEXRAD3 Example"
},
{
"location":"/edex/data-purge/#frame-based-purge",
"text":"Some plugins use frame-base purging, retaining and certain number of prpduct \"versions\". /awips2/edex/data/utility/common_static/base/purge/satellitePurgeRules.xml purgeRuleSet \n key sectorID /key \n key physicalElement /key \n defaultRule \n versionsToKeep 196 /versionsToKeep \n /defaultRule \n rule \n keyValue NEXRCOMP /keyValue \n versionsToKeep 288 /versionsToKeep \n /rule \n rule \n keyValue Alaska National /keyValue \n versionsToKeep 48 /versionsToKeep \n /rule In the above example, notice a default rule (196) as well as specific sectors with their own rules.",
"title":"Frame-based purge"
},
{
"location":"/edex/data-purge/#purge-logs",
"text":"Data purge events are logged to the file edex-ingest-purge- yyyymmdd .log , where yyyymmdd is the date stamp. tail -f edex-ingest-purge-20120327.log\n\n--------START LOG PURGE---------\nINFO 2012-03-27 00:30:00,027 [DefaultQuartzScheduler_Worker-3] PurgeLogger: EDEX - PURGE LOGS::Skipped file with invalid fileName: afos-trigger.log\nINFO 2012-03-27 00:30:00,193 [DefaultQuartzScheduler_Worker-3] PurgeLogger: EDEX - PURGE LOGS::Removed 1 old files\nINFO 2012-03-27 00:31:23,155 [DefaultQuartzScheduler_Worker-3] PurgeLogger: EDEX - PURGE LOGS::Archived 14 files\nINFO 2012-03-27 00:31:23,155 [DefaultQuartzScheduler_Worker-3] PurgeLogger: EDEX - PURGE LOGS::Skipped processing 1 files\nINFO 2012-03-27 00:31:23,155 [DefaultQuartzScheduler_Worker-3] PurgeLogger: EDEX - PURGE LOGS::---------END LOG PURGE-----------",
"text":"To see all purge rule directories (base, site, region, configured): find /awips2/edex/data/utility -name purge\n\n/awips2/edex/data/utility/edex_static/region/CR/purge\n/awips2/edex/data/utility/edex_static/base/purge\n/awips2/edex/data/utility/edex_static/configured/OAX/purge\n/awips2/edex/data/utility/edex_static/site/OAX/purge\n/awips2/edex/data/utility/common_static/region/CR/purge\n/awips2/edex/data/utility/common_static/base/purge\n/awips2/edex/data/utility/common_static/configured/OAX/purge\n/awips2/edex/data/utility/common_static/site/AFC/purge\n/awips2/edex/data/utility/common_static/site/OAX/purge To see a list of the data plug-ins that have purge rules: find /awips2/edex/data/utility -name \"*PurgeRules.xml\"\n\n/awips2/edex/data/utility/edex_static/base/purge/airmetPurgeRules.xml\n/awips2/edex/data/utility/edex_static/base/purge/convsigmetPurgeRules.xml\n/awips2/edex/data/utility/common_static/base/purge/bufruaPurgeRules.xml\n/awips2/edex/data/utility/common_static/base/purge/obsPurgeRules.xml\n/awips2/edex/data/utility/common_static/base/purge/nctextPurgeRules.xml\n/awips2/edex/data/utility/common_static/base/purge/ncscatPurgeRules.xml\n/awips2/edex/data/utility/common_static/base/purge/vaaPurgeRules.xml\n/awips2/edex/data/utility/common_static/base/purge/bufrmosHPCPurgeRules.xml\n/awips2/edex/data/utility/common_static/base/purge/bufrhdwPurgeRules.xml\n/awips2/edex/data/utility/common_static/base/purge/cwaPurgeRules.xml\n/awips2/edex/data/utility/common_static/base/purge/airmetPurgeRules.xml\n/awips2/edex/data/utility/common_static/base/purge/ffmpPurgeRules.xml\n/awips2/edex/data/utility/common_static/base/purge/lsrPurgeRules.xml\n/awips2/edex/data/utility/common_static/base/purge/profilerPurgeRules.xml\n/awips2/edex/data/utility/common_static/base/purge/poessoundingPurgeRules.xml\n/awips2/edex/data/utility/common_static/base/purge/gpdPurgeRules.xml\n/awips2/edex/data/utility/common_static/base/purge/mcidasPurgeRules.xml\n/awips2/edex/data/utility/common_static/base/purge/acarssoundingPurgeRules.xml\n/awips2/edex/data/utility/common_static/base/purge/ffgPurgeRules.xml\n/awips2/edex/data/utility/common_static/base/purge/sgwhvPurgeRules.xml\n/awips2/edex/data/utility/common_static/base/purge/intlsigmetPurgeRules.xml\n/awips2/edex/data/utility/common_static/base/purge/aggregatePurgeRules.xml\n/awips2/edex/data/utility/common_static/base/purge/radarPurgeRules.xml\n/awips2/edex/data/utility/common_static/base/purge/idftPurgeRules.xml\n/awips2/edex/data/utility/common_static/base/purge/wcpPurgeRules.xml\n/awips2/edex/data/utility/common_static/base/purge/warningPurgeRules.xml\n/awips2/edex/data/utility/common_static/base/purge/satellitePurgeRules.xml\n/awips2/edex/data/utility/common_static/base/purge/sshaPurgeRules.xml\n/awips2/edex/data/utility/common_static/base/purge/ldadhydroPurgeRules.xml\n/awips2/edex/data/utility/common_static/base/purge/ldadmesonetPurgeRules.xml\n/awips2/edex/data/utility/common_static/base/purge/ccfpPurgeRules.xml\n/awips2/edex/data/utility/common_static/base/purge/atcfPurgeRules.xml\n/awips2/edex/data/utility/common_static/base/purge/bufrssmiPurgeRules.xml\n/awips2/edex/data/utility/common_static/base/purge/sgwhPurgeRules.xml\n/awips2/edex/data/utility/common_static/base/purge/geomagPurgeRules.xml\n/awips2/edex/data/utility/common_static/base/purge/modelsoundingPurgeRules.xml\n/awips2/edex/data/utility/common_static/base/purge/bufrmosAVNPurgeRules.xml\n/awips2/edex/data/utility/common_static/base/purge/ncuairPurgeRules.xml\n/awips2/edex/data/utility/common_static/base/purge/acarsPurgeRules.xml\n/awips2/edex/data/utility/common_static/base/purge/airepPurgeRules.xml\n/awips2/edex/data/utility/common_static/base/purge/bufrquikscatPurgeRules.xml\n/awips2/edex/data/utility/common_static/base/purge/cwatPurgeRules.xml\n/awips2/edex/data/utility/common_static/base/purge/nonconvsigmetPurgeRules.xml\n/awips2/edex/data/utility/common_static/base/purge/pirepPurgeRules.xml\n/awips2/edex/data/utility/common_static/base/purge/statsPurgeRules.xml\n/awips2/edex/data/utility/com
"text":"To see a list of clients connecting to your EDEX server, use the \nedex users [YYYYMMDD]\n command, where \nYYYYMMDD\n is the optional date string.\n\n\nedex users\n\n -- EDEX Users 20160826 --\nuser@101.253.20.225\nuser@192.168.1.67\nawips@0.0.0.0\nawips@sdsmt.edu\n...\n\n\n\nLogging Daily EDEX Users\n\uf0c1\n\n\nCreate a short script to run once daily at 20 minutes after 00 UTC, appending each day's \nedex users\n list to a logfile \n/home/awips/edex-users.log\n.\n\n\n\n\n\n\nvi ~/edexUsers.sh\n\n\n#!/bin/bash\n/awips2/tools/bin/edex users \n /home/awips/edex-users.log\n\n\n\n\n\n\n\ncrontab -e\n\n\n0 20 * * * /home/awips/edexUsers.sh 1\n /dev/null 2\n1",
"text":"Create a short script to run once daily at 20 minutes after 00 UTC, appending each day's edex users list to a logfile /home/awips/edex-users.log . vi ~/edexUsers.sh #!/bin/bash\n/awips2/tools/bin/edex users /home/awips/edex-users.log crontab -e 0 20 * * * /home/awips/edexUsers.sh 1 /dev/null 2 1",
"text":"Several of the data sets in the Obs menu can be interrogated (sampled) for more detailed information by clicking mouse Button 1 (B1) over a site. These data sets include METAR, Maritime, and Local. The Obs menu is subdivided into sections that contain related products. These sections are described below.\n\n\nMETAR\n\uf0c1\n\n\nThis section contains automatically updating METAR observations, ceiling and visibility plots, wind chill and heat indices, precipitation plots at various time intervals, and quality-checked MSAS observations. The 24hr Chg METAR plot provides the difference between the observed temperature, dewpoint, pressure, and wind from those observed 24 hours earlier. The calculation of the wind difference involves vector subtraction of the \"u\" and \"v\" components.\n\n\nSynoptic\n\uf0c1\n\n\nThis section contains automatically updating Synoptic observations, and 6 hour and 24 hour precip plots. Note that this section of the menu is not present at most sites.\n\n\nMaritime\n\uf0c1\n\n\nThis section contains buoy and ship report plots, plus SAFESEAS for the Marine WFOs.\n\n\n\n\nMAROB\n displays include Station Plots\n\n\nThe \nOther Maritime Plots\n cascading menu contains options to display the Fixed and Moving Sea State plots, MAROB Sea State and Cloud/Vis plots, Maritime Clouds/Visibility plots, as well as the Scatterometer Winds.\n\n\nSea State\n plots provide information on the wave period and height and swell period and height. The wave type, whether a standard wave or a wind wave, is denoted at the origin of the plot by a \"+\" or a \"w\", respectively. An \"x\" at the plot origin signifies that no wave type was reported. If reported, the directions of the primary and secondary swells are denoted with arrows labeled \"1\" and \"2\",respectively.Thearrowspointinthedirectiontheswellismoving.\n\n\nMaritimeClouds/Visibility\nplotscontainastationcircledenotingskycoverageandthevisibilityalongwithstandardsymbolsforobstructionstovisibility.\n\n\nScatterometerWinds\nareobtainedfromtheASCATinstrumentonEUMETSAT'sMetOp-Apolarorbitingsatellite.Thisinstrumentsendspulsesofradiationtotheoceansurfaceandmeasurestheamountofenergy,calledbackscatter,itreceivesback.Whenyousampletheseobservations,thetime,satelliteID,winddirection,andwindspeedareprovided.Withthepolarorbitingscanning,agivenregionwillgenerallybesampledaboutevery12hours.ASCATWinds(25kmretrievalresolutionbutinterpolatedanddisplayedat12.5kmresolution)canbelaunchedfromeithertheCAVEObsmenuorfromtheSatellitemenuYoucanaccesstheScatterometerWindsmenuoptionsbyselecting\nSurface\n\n\nOtherMaritimePlots\n\n\nScatterometerWinds\n.TheASCATScatterometerOceanWindsproductisdisplayableonCAVEatallscales:N.Hemisphere,NorthAmerica,CONUS,Regional,State(s),andWFO.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nLocalStormReports\n:LocalStormReport(LSR)plotsaregeneratedfromspotterreports\nthatwereenteredintotheLSRtextdatabaseanddecodedintothecorrectpointdataformat.TheLSRgraphicaluserinterface(GUI)isastand-aloneAWIPSapplicationdesignedtoprovideforecasterswithaneasyandquickwaytocreate,manage,andsendtheLSRpublictextproduct.Thistextproductcontainsnoteworthyweathereventsforwhichtheforecasterhaseitherreceivedorsoughtoutreal-timeobservations.\n\n\n\n\nNationalConvectiveWeatherForecast(AWC)\n\uf0c1\n\n\nThe\nNationalConvectiveWeatherForecast\n(NCWF)isanautomaticallygenerateddepictionofcurrentconvectionandextrapolatedsignificantcurrentconvection.Itisasupplementto,butdoesnotsubstitutefor,thereportandforecastinformationcontainedin\nConvectiveSIGMETs\n.TheNCWFcontainsbothGRIBandBUFRoutput.TheGRIBoutputdelineatesthecurrentconvection.TheBUFRoutputincludeshazardousconvectionareapolygons,movementarrows,andstormtopandspeedtextinformation.\n\n\nTheNCWFdisplaybunlderenders\nstormto
"text":"This section contains automatically updating METAR observations, ceiling and visibility plots, wind chill and heat indices, precipitation plots at various time intervals, and quality-checked MSAS observations. The 24hr Chg METAR plot provides the difference between the observed temperature, dewpoint, pressure, and wind from those observed 24 hours earlier. The calculation of the wind difference involves vector subtraction of the \"u\" and \"v\" components.",
"text":"This section contains automatically updating Synoptic observations, and 6 hour and 24 hour precip plots. Note that this section of the menu is not present at most sites.",
"text":"This section contains buoy and ship report plots, plus SAFESEAS for the Marine WFOs. MAROB displays include Station Plots The Other Maritime Plots cascading menu contains options to display the Fixed and Moving Sea State plots, MAROB Sea State and Cloud/Vis plots, Maritime Clouds/Visibility plots, as well as the Scatterometer Winds. Sea State plots provide information on the wave period and height and swell period and height. The wave type, whether a standard wave or a wind wave, is denoted at the origin of the plot by a \"+\" or a \"w\", respectively. An \"x\" at the plot origin signifies that no wave type was reported. If reported, the directions of the primary and secondary swells are denoted with arrows labeled \"1\" and \"2\", respectively. The arrows point in the direction the swell is moving. Maritime Clouds/Visibility plots contain a station circle denoting sky coverage and the visibility along with standard symbols for obstructions to visibility. Scatterometer Winds are obtained from the ASCAT instrument on EUMETSAT's MetOp-A polar orbiting satellite. This instrument sends pulses of radiation to the ocean surface and measures the amount of energy, called backscatter, it receives back. When you sample these observations, the time, satellite ID, wind direction, and wind speed are provided. With the polar orbiting scanning, a given region will generally be sampled about every 12 hours. ASCAT Winds (25 km retrieval resolution but interpolated and displayed at 12.5 km resolution) can be launched from either the CAVE Obs menu or from the Satellite menu You can access the Scatterometer Winds menu options by selecting Surface Other Maritime Plots Scatterometer Winds . The ASCAT Scatterometer Ocean Winds product is displayable on CAVE at all scales: N. Hemisphere, North America, CONUS, Regional, State(s), and WFO. Local Storm Reports : Local Storm Report (LSR) plots are generated from spotter reports\nthat were entered into the LSR text database and decoded into the correct point data format. The LSR graphical user interface (GUI) is a stand-alone AWIPS application designed to provide forecasters with an easy and quick way to create, manage, and send the LSR public text product. This text product contains noteworthy weather events for which the forecaster has either received or sought out real-time observations.",
"text":"The National Convective Weather Forecast (NCWF) is an automatically generated depiction of current convection and extrapolated significant current convection. It is a supplement to, but does not substitute for, the report and forecast information contained in Convective SIGMETs . The NCWF contains both GRIB and BUFR output. The GRIB output delineates the current convection. The BUFR output includes hazardous convection area polygons, movement arrows, and storm top and speed text information. The NCWF display bunlde renders storm tops and movement , previous performance polygons , 1-hour extrapolation polygons , and current convective interest grid (colorbar).",
"text":"The CWA is an aviation weather warning for conditions meeting or approaching national in-flight advisory (AIRMET, SIGMET or SIGMET for convection) criteria. The CWA is primarily used by air crews to anticipate and avoid adverse weather conditions in the en route and terminal environments. It is not a flight planning product because of its short lead time and duration. Shown with NEXRAD DHR composite:",
"text":"These plots are derived from the MOS BUFR Bulletins. The previous MOS plots were derived from the MOS Text Bulletins. The plots display forecast data for GFS MOS, GFS-Extended MOS, and NGM MOS. Submenus under each model reveal the element choices. These displays include: Station Model Plots (Wind, T, Td, Sky Cover, Wx) MaxT/MinT (\u00b0F) Ceiling (agl) / Visibility (ft \u00d7 100) (Categorical) Probabilities Submenu (6h/12h PoP, 6h/12h Tstorm, 6h/12h Svr-Tstorm, Conditional precipitation types; %) QPF 12h (Categorical mid-points; inches) QPF 6h (Categorical mid-points; inches) Snowfall (6h/12h/24h, Categorical; inches)",
"text":"This menu item provides three options for displaying lightning flash plots over specified 1 minute, 5 minute, 15 minute and 1 hour intervals. USPLN (United States Precision Lightning Network) : WSI Corporation USPLN lightning data has been made available exclusively to universities for education and research use. Unidata serves USPLN lightning stroke data from the LIGHTNING LDM data feed. Registration is required to request this data, and the free feed is available on an annually renewed basis. USPLN data is not available to the public. NLDN (National Lightning Detection Network) : The NLDN option plots cloud-to-ground (CG) lightning flashes for specified time intervals across the continental United States. NLDN lightning data can be displayed as a grid image displaying the cloud-to-ground density values for a selected resolution (1km, 3km, 5km, 8km, 20km, and 40km). GLD (Global Lightning Dataset) : The GLD option plots cloud-to-ground (CG) lightning flashes for specified time intervals on a global-scale. GLD lightning data can also be displayed as a grid image displaying the cloud-to-ground density values for a selected resolution (1km, 3km, 5km, 8km, 20km, and 40km). ENI Total Lightning : In addition to displaying CG lightning flashes, the Total Lightning option also displays Cloud Flash (CF) lightning and Pulses. CF lightning are lightning flashes which do not strike the ground such as in-cloud, cloud-to-cloud, and cloud-to-air lightning. Lightning pulses are electromagnetic pulses that radiate outward from the lightning channel. ENI total lightning data can be displayed as a grid image displaying the cloud-to-ground, cloud flash, and lightning pulse density values for a selected resolution (1km, 3km, 5km, 8km, 20km, and 40km).",
"text":"VIIRS is one of five instruments onboard the NPP satellite. VIIRS' mission is to collect radiometric imagery in visible and infrared wavelengths of the Earth's surface; this includes observing fires, ice, ocean color, vegetation, clouds, and land and sea surface temperatures, and supplying high-resolution images and data used by meteorologists to assess climate change and improve short-term weather forecasting. The VIIRS submenu option provides VIIRS imagery and moderate band satellite displays for the\nCONUS, Alaska, and Pacific regions. In addition to accessing the NPP Product VIIRS data via the Satellite menu, the VIIRS Imagery data can also be accessed using the Product Browser .",
"text":"GOES and POES Sounding Data Availability Plots displays the locations where GOES and POES temperature and moisture profiles are available. These soundings are displayed on a Skew-T/log P chart using the Points tool and the Volume Browser. Soundings from the GOES satellites are made only in relatively cloud-free areas, whereas POES systems produce temperature and moisture soundings in clear and cloudy atmospheres. Each hour, NESDIS provides the latest soundings from GOES East and West. Although the GOES East and West sounders yield soundings over a broad area, the default AWIPS configuration retains soundings only from within each site's Regional CAVE scale domain. POES soundings are generated approximately every 12 hours and have more global coverage.",
"title":"GOES and POES Sounding Data"
},
{
"location":"/cave/d2d-satellite/#poes-imagery",
"text":"The POES Imagery section of the Satellite menu contains selectors for IR Window, Visible, 3.7\u00b5, and 11-3.7\u00b5 products. These are viewable on all scales.",
"text":"The products available from the Sounder Imagery submenu are based purely on the imager instruments aboard the GOES East (GE) and GOES West (GW) satellites.",
"text":"A variety of precipitation products are accessible from the Derived Products submenu. These products are derived from one or more of the various satellites (e.g., DMPS, POES, GOES, and GPS). Descriptions of the products follow. The Blended Rain Rate (formerly Rainfall Rate) product is produced hourly to gather recent rain rate retrievals from passive microwave instruments on six polar-orbiting satellites. The blended rain rate eliminates the bias between those data sets and provides a unified, meteorologically significant rain rate field to weather forecasters. The GOES products derived from the GOES satellite include Lifted Index, Total Precip Water (TPW), Cloud Amount, Cloud Top Height, Skin Temperature, and Low Cloud Base. Because the imagery from these products is based on the GOES sounder instrument, several important differences exist between these products and the other (imager-based) imagery. The main differences are that the resolution is no finer than 10 km, the product update frequency is driven by the sounder instrument (AWIPS receives a set of GOES East/West composite derived product images once per hour), and the aerial coverage is based on that of the sounder scans, which is somewhat less than the aerial coverage provided by the imager. Descriptions of the products follow. Lifted Index is a common measure of instability. Its value is obtained by computing the temperature that air near the ground would have if it were lifted to some higher level (usually around 18,000 feet), and comparing that temperature to the actual temperature at that level. The more negative the value, the more instability there is. Total Precip Water is the vertically integrated water vapor content in a column extending from the earth's surface to the top of the atmosphere. Cloud Amount provides an hourly update of cloud amounts within a geostationary satellite field of view. You can loop through the display to identify increasing/decreasing cloud conditions and trends. Cloud Top Height is the height of the cloud in thousands of feet (base - top). Skin Temperature is the sea surface temperature of the ocean surface water. Low Cloud Base provides nighttime images of fog and low stratus clouds derived from a combination of two GOES IR channels. This product identifies cloud ceilings of 1000 feet and is generated hourly starting between 2042 and 2142 GMT, and ending between 1510 and 1610 GMT the next day. This product is beneficial to the warning and forecast processes specific to aviation and terminal forecasting The Total Precip Water (TPW) value can also be derived from the data sources of DMSP, SSM/I (Defense Meteorological Satellite Program Special Sensor Microwave / Imager), and POES AMSU (POES Advanced Microwave Sounding Unit) satellites, which are accessed from the DMSP SSM/I, and POES AMSU sections of the submenu. Variations of TPW (\"Blended Total Precip Water\" and \"Percent of Normal TPW\") are selectable\nunder the AMSU and SSM/I + GPS section. The Blended Total Precip Water product is a blend of the various data sources of AMSU,\nSSM/I, and GPS satellites, and can be over water or land. The Percent of Normal TPW product is calculated at various times (hourly, monthly,\nseasonally, etc.) to determine departures from the normal. From the information obtained,\nforecasters can predict the chances of having a below average, normal, or above average\nprecipitation in the upcoming months.",
"text":"GOES High Density Winds submenu has options to display satellite-derived multi-layer winds plots from the IR, Visible, and three Water Vapor channels. In addition, you can display individual layers that display a composite of all the satellite channels.",
"text":"Scatterometer Winds are obtained from the ASCAT instrument on EUMETSAT's MetOP-A polar orbiting satellite. This instrument sends pulses of radiation to the ocean surface and measures the amount of energy, called backscatter, it receives back. When you sample these observations, the time, satellite ID, wind direction, and wind speed are provided. With the polar orbiting scanning, a given region will generally be sampled about every 12 hours. ASCAT winds (25 km retrieval resolution but interpolated and displayed at 12.5 km resolution) are launchable from both the CAVE Satellite menu and the Upper Air menu. The ASCAT instrument generates ocean surface wind retrievals. The ASCAT Scatterometer Ocean Winds product is displayable on\nCAVE at all scales.",
"text":"The Unidata D2D Perspective features a selectable NEXRAD station display over a loop of the FNEXRAD Digital Hybrid Reflectivity product. Selecting any station will open a two-panel reflectivity and velocity view for the selected station.",
"text":"Individual NEXRAD station menus are accessible in Radar NEXRAD Stations and are grouped alphabetically for a condensed submenu structure. With only the NEXRAD3 feedtype (NEXAD2 being disabled), notice that only some of the menu items will out with available data.",
"title":"NEXRAD & TDWR Station Menus"
},
{
"location":"/cave/d2d-radar/#best-res-zsrm8-zv",
"text":"The radar combination products Z+SRM and Z+V are precombined formats of the reflectivity and storm relative motion or velocity, displayed together via a single menu selection. SRM products include the storm motion vector information, which is plotted in the upper left corner of the Main Display Pane.",
"text":"This section enables you to load multiple base and dual-pol products, which are then simultaneously displayed. The label of this section of the menu describes the format for loading the products: Z+SRM in the upper left quadrant, ZDR+V in the upper right quadrant, KDP+HC in the lower left quadrant, and CC+SW in the lower right quadrant. Primary dual-pol base data analysis is best accomplished using the All Tilts base data option (4 panel all tilts with 8 products loaded), though you may use the single tilts (e.g., 0.5 base data) for longer time duration loops. To load 4 panel displays containing multiple elevation angles of the same product, you would\nselect the four panel option and then select the desired set of 4 panels from the four\npanel submenu. All Tilts allows you to step or animate in either space or time. Selecting one of the All Tilts buttons will load all the tilts available from the latest volume scan. It will continue to load tilts from previous volume scans until it has loaded as many frames as indicated on the frame count menu. Auto updates will add higher tilts from the latest volume scan, replacing a tilt from the oldest volume. After loading an All Tilts display, Shift + LEFT ARROW and Shift + RIGHT ARROW and looping will take you through the frames in the order in which the system loaded them (without regard to volume scan or tilt). The UP ARROW and DOWN ARROW will step the display up or down in a volume scan allowing the tilts to change for a fixed time. The RIGHT ARROW and LEFT ARROW will step the display forward or backward through time at a fixed tilt. Once you have set the mode of motion (vertical or time), the Page Up/Page Down keys will start and adjust loop speed. To switch from vertical to time mode or from time to vertical mode, press the desired arrow key. If you hit the up or down arrow key in a standard (not All-Tilts) display, looping and stepping are disabled until you hit either the left or right arrow key or one of the stepping buttons on the menu. Once an arrow key (Left, Right, Up, Down) has been pressed, the stepping/animation controls on the main window toolbar and the Page Up/Page Down keys will function in that same mode. For example, assume the UP ARROW or DOWN ARROW key is pressed; the menu controls will now operate through the tilts at a fixed time, e.g., you can go to the lowest tilt by selecting the First Frame iconified button.",
"text":"This section is divided into two parts. The upper part lists individual products: four base products and three dual-pol products (ZDR, CC, and KDP). The lower part includes submenus for accessing multiple products and applications. The following describes the submenus grouped in the lower part of the Best Res Base Products section. Precip : In addition to the QPE dual-pol products, this submenu includes the legacy precip products, which include Storm Total, One Hour, Three Hour, and User Selectable precipitation products. A suite of snowfall products is also available on the Precip submenu. All are available for request (OTR, RMR), and the first four can be added to an RPS (Routine Product Set) list. All of these products are available on any scale. Derived Products : The Derived Products submenu includes Layer Reflectivity, Cross Section, and Other products displayed on any scale. Derived products include precipitation, storm (mesocyclone, hail, tornado), and wind derivations. Algorithm Overlays : The Algorithm Overlays submenu includes legacy algorithm overlays and the ML dual-pol overlay. four panel : The four panel submenu includes menu entries for Z+V, Z+SRM 8- and 4-bit, and some other combinations that are presented in 4-panel mode, with a different elevation angle or product in each panel. Data Quality : The Data Quality products, accessible by a pull-right submenu, include Clutter Filter Control and reflectivity and velocity clutter probability products. 4-bit/Legacy Prods : The 4-bit/Legacy Prods submenu uses generic selectors that load 8-bit (256 level) data, with legacy 4-bit (16 level) and 3-bit (8 level) data filling in when no 8-bit data is available. Radar Applications : The Radar Applications submenu provides access to all the radar applications and radar tools.",
"title":"Best Res Base Products"
},
{
"location":"/cave/d2d-radar/#mrms",
"text":"",
"title":"MRMS"
},
{
"location":"/cave/d2d-radar/#fnexrad-composites",
"text":"",
"title":"FNEXRAD Composites"
},
{
"location":"/cave/d2d-radar/#dhr",
"text":"",
"title":"DHR"
},
{
"location":"/cave/d2d-radar/#dlv",
"text":"",
"title":"DLV"
},
{
"location":"/cave/d2d-radar/#eet",
"text":"",
"title":"EET"
},
{
"location":"/cave/d2d-radar/#hhc",
"text":"",
"title":"HHC"
},
{
"location":"/cave/d2d-radar/#daa",
"text":"",
"title":"DAA"
},
{
"location":"/cave/d2d-radar/#dta",
"text":"",
"title":"DTA"
},
{
"location":"/cave/d2d-radar/#mosaic-radar-plots",
"text":"Mosaics available via this menu use data from up to nine nearby radars. Additional optional\nmosaics on cascading menus provide a limited list of radar products from a predefined set of WSR-88D radars within a given region. Your System Manager or site Administrator can set up such mosaics by: /awips2/edex/data/utility/common_static/site/ SITE /radar/radarInUse.txt . A mosaicInfo.txt table will only work while logged on to an AWIPS workstation.",
"text":"A velocity (V) display from the radar shows only the radial component of the wind, so the indicated\nspeed depends on the direction of the wind and the azimuth (direction) from the radar. Consider, for example, a north wind. Straight north of the radar, the full speed of the wind will be seen on the V product. As one moves around to the east of the radar, the radial component gets smaller, eventually reaching zero straight east of the radar. If the wind direction is known, then the actual wind speed can be computed by dividing the observed radial speed by the cosine of the angle between the radar radial and the actual direction. The EAV tool allows you to provide that angle and use the sampling function of the display to show the actual wind speed.",
"text":"The Four-dimensional Stormcell Investigator (FSI) was developed by the National Severe Storms Laboratory for its Warning Decision Support System Integrated Information. This technology allows users to create and manipulate dynamic cross-sections (both vertical and at constant altitude), such that one can \u201cslice and dice\u201d storms and view these data in three-dimensions and across time.",
"text":"This tool is used in conjunction with Doppler velocity data to calculate the velocity difference (or \"shear\") of the data directly under the end points. As with the Baselines, this feature comes up editable and the end points can be dragged to specific gates of velocity data. When in place, the speed difference (kts), distance between end points (nautical miles), shear (s-1), and distance from radar (Nmi) are automatically plotted next to the end points and in the upper left corner of the Main Display Pane. A positive shear value indicates cyclonic shear, while a negative value indicates anticyclonic shear. If either end point is not directly over velocity data, the phrase \"no data\" is reported for the shear value. This tool is also useful in determining gate-to-gate shear. Simply place the two end points directly over adjacent gates of velocity data. \"Snapping\" VR Shear : If you are zoomed in over an area when you load VR - Shear, and the VR - Shear Baseline does not appear, click B3 to \"snap\" the Baseline to where the mouse cursor\nis located. VR - Shear in 4 Panel : You can use the VR - Shear Tool when the large display is in 4 panel\nmode. The VR - Shear overlay is loaded in different colors for each panel. There are actually\nfour copies of the program running, and each behaves independently. This means that you can\nget accurate readings in any one of the four panels \u2014 one VR - Shear panel is editable at a time. To activate, click B2 on the VR - Shear legend in the desired panel and position the query line to\nthe echoes of interest.",
"title":"V-R Shear"
},
{
"location":"/cave/d2d-uair/",
"text":"The Upper Air dropdown menu provides access to upper air plots, profiler data, radar plan-view and perspective displays of winds, and aircraft and rawinsonde data. Nearby Radiosonde Observations (RAOB) are also included on the menu to provide easy viewing of upper air data.\n\n\nNSHARP Upper Air Soundings\n\uf0c1\n\n\n\n\nRAOB data is plotted on the standard Skew-T log-p thermodynamic diagram. A small reference map indicating the location(s) of the plotted sounding(s) is provided in the upper left corner of the main display pane. If you overlay another Skew-T whose location is far from the original sounding location, the reference map updates to show both locations.\n\n\n\n\n\n\nNUCAPS Soundings\n\uf0c1\n\n\n\n\nThe NOAA Unique CrIS/ATMS Processing System (\nNUCAPS\n) soundings are derived from processing of CrIS/ATMS data, provides cloud cleared radiances and trace gas that enable increased accuracy in the development of the vertical profile of temperature and water vapor retrievals. By clicking on the individual dots, the forecaster is able to render the sounding for the selected point using the \nNSHARP plugin\n.\n\n\n\n\n\n\nUpper Air Plots\n\uf0c1\n\n\n\n\nNCEP: 200mb to 850mb\n\n\nRAOB: 150mb to 925mb\n\n\n\n\n\n\n\n\nUKMO 500mb Height\n\uf0c1\n\n\n500mb height graphic out to 144 forecast hours.\n\n\n\n\n\n\nCPC Charts\n\uf0c1\n\n\n\n\n6-10 day mean 500mb Height\n\n\n8-14 day mean 500mb Height\n\n\n6-10 day 500mb Height Anomaly\n\n\n8-14 day 500mb Height Anomaly\n\n\n\n\n\n\n\n\nNPN Profiler Time-Height\n\uf0c1\n\n\nNOAA Profiler Network (\nNPN\n) observations as a time-series plot. This time-series plugin is also used in the \nVolume Browser\n plugin for both grids and observations.\n\n\n\n\n\n\nNPN Profiler Plot\n\uf0c1\n\n\n\n\n200hPa-925hPa\n\n\n1500m-500m AGL\n\n\nSurface\n\n\n\n\n\n\nRadar VWP Height-Level\n\uf0c1\n\n\n\n\n15km AGL\n\n\n14km AGL\n\n\n13km AGL\n\n\n...\n\n\n500m AGL\n\n\n250m AGL\n\n\n100m AGL\n\n\n\n\n\n\nRadar VWP Pressure-Level\n\uf0c1\n\n\n\n\n200hPa to 925hPa\n\n\n\n\n\n\nPIREP Aircraft Plot\n\uf0c1\n\n\nThe Aircraft data includes Low-, Mid-, and High-level Pilot Weather Report (PIREP) observations. The display plots the temperature, aircraft identifier, wind speed and direction, significant weather, and the flight level (in feet). Pilot reports are critical for air safety. Pilots reports on the conditions they are experiencing show up in a matter of minutes on AWIPS. Weather conditions can change quickly, and there is nothing like having a pilot report to provide a bird's eye view of what it is really like up there. PIREPs may validate forecast conditions, or they may describe real-time weather that varies from them.\n\n\n\n\nIcing: Low Level, Mid Level, High Level\n\n\nTubulence: Low Level Mid Level, High Level\n\n\n\n\n\n\n\n\nAircraft MDCRS\n\uf0c1\n\n\nMeteorological Data Collection and Reporting System (MDCRS) data includes plan-view plots for various 5kft layers and ascent/descent soundings. Using the availability plots (Upper Air menu under MDCRS plots) and ACARS Airports from the Maps menu button you can locate airports that have available soundings. ACARS Airports provides an illustration of locations of airports, but it is not necessary to use it. The \"+\" sign means a temperature sounding and the \"*\" means a temperature and dewpoint sounding. To see a sounding at a location, simply press the Points menu button. Several points from letters of the alphabet will appear on the map display. To view a sounding, drag one of the points/letters to a \"+\" or \"*\"location.FromthemenubarpressVolumeandthenBrowser.FromtheVolumeBrowserselectMDCRSforSource,SoundingforFieldsandselecttheletter/pointonthedesiredlocationforPoints.ClickonyourselectionintheProductSelectionListandthenpresstheLoadbuttontoviewthesounding.\n\n\nAzoomableinsetmap(NWcorner)isavailabletoshowthelocationofthesounding.WhenyouzoominbyclickingmouseButton2(B2),theflighttrackoftheascent/descentsoundingisshownonthemap
"text":"RAOB data is plotted on the standard Skew-T log-p thermodynamic diagram. A small reference map indicating the location(s) of the plotted sounding(s) is provided in the upper left corner of the main display pane. If you overlay another Skew-T whose location is far from the original sounding location, the reference map updates to show both locations.",
"title":"NSHARP Upper Air Soundings"
},
{
"location":"/cave/d2d-uair/#nucaps-soundings",
"text":"The NOAA Unique CrIS/ATMS Processing System ( NUCAPS ) soundings are derived from processing of CrIS/ATMS data, provides cloud cleared radiances and trace gas that enable increased accuracy in the development of the vertical profile of temperature and water vapor retrievals. By clicking on the individual dots, the forecaster is able to render the sounding for the selected point using the NSHARP plugin .",
"title":"NUCAPS Soundings"
},
{
"location":"/cave/d2d-uair/#upper-air-plots",
"text":"NCEP: 200mb to 850mb RAOB: 150mb to 925mb",
"title":"Upper Air Plots"
},
{
"location":"/cave/d2d-uair/#ukmo-500mb-height",
"text":"500mb height graphic out to 144 forecast hours.",
"title":"UKMO 500mb Height"
},
{
"location":"/cave/d2d-uair/#cpc-charts",
"text":"6-10 day mean 500mb Height 8-14 day mean 500mb Height 6-10 day 500mb Height Anomaly 8-14 day 500mb Height Anomaly",
"text":"NOAA Profiler Network ( NPN ) observations as a time-series plot. This time-series plugin is also used in the Volume Browser plugin for both grids and observations.",
"text":"The Aircraft data includes Low-, Mid-, and High-level Pilot Weather Report (PIREP) observations. The display plots the temperature, aircraft identifier, wind speed and direction, significant weather, and the flight level (in feet). Pilot reports are critical for air safety. Pilots reports on the conditions they are experiencing show up in a matter of minutes on AWIPS. Weather conditions can change quickly, and there is nothing like having a pilot report to provide a bird's eye view of what it is really like up there. PIREPs may validate forecast conditions, or they may describe real-time weather that varies from them. Icing: Low Level, Mid Level, High Level Tubulence: Low Level Mid Level, High Level",
"title":"PIREP Aircraft Plot"
},
{
"location":"/cave/d2d-uair/#aircraft-mdcrs",
"text":"Meteorological Data Collection and Reporting System (MDCRS) data includes plan-view plots for various 5kft layers and ascent/descent soundings. Using the availability plots (Upper Air menu under MDCRS plots) and ACARS Airports from the Maps menu button you can locate airports that have available soundings. ACARS Airports provides an illustration of locations of airports, but it is not necessary to use it. The \"+\" sign means a temperature sounding and the \"*\" means a temperature and dewpoint sounding. To see a sounding at a location, simply press the Points menu button. Several points from letters of the alphabet will appear on the map display. To view a sounding, drag one of the points/letters to a \"+\" or \"*\" location. From the menu bar press Volume and then Browser. From the Volume Browser select MDCRS for Source, Sounding for Fields and select the letter/point on the desired location for Points. Click on your selection in the Product Selection List and then press the Load button to view the sounding. A zoomable inset map (NW corner) is available to show the location of the sounding. When you zoom in by clicking mouse Button 2 (B2), the flight track of the ascent/descent sounding is shown on the map. In addition, you can sample the flight track to see the time and elevation. To zoom out, click mouse Button 1 (B1). This inset map (and also those on var vs. height displays, cross sections, and cell trends) can be suppressed by setting the global density (i.e., from the tool bar) at less than 1. 000-500hft in 50ft increments 1 hour profile availability 6 hour profile availability",
"title":"SIGMET and AIRMET reports: Convective, Icing, Turbulance, Tropical, Volcanic"
},
{
"location":"/cave/d2d-uair/#sigmet",
"text":"SIGMET (Significant Meteorological Information) is an alphanumeric message describing specific aviation hazard conditions between the surface and 45,000 feet (FL450). A SIGMET includes information about the location of the hazard using VOR locations. SIGMETs are produced on an as-needed basis at the AWC and are distributed on the SBN.",
"title":"SIGMET"
},
{
"location":"/cave/d2d-uair/#airmet",
"text":"AIRMET (Airmen's Meteorological Information) is an alpha-numeric message describing specific aviation hazard conditions between the surface and 45,000 feet (FL450), but not requiring the issuance of a SIGMET. An AIRMET includes information about the location of the hazard using VOR locations. AIRMETs are produced every 6 hours at the AWC for the CONUS area, and are distributed on the SBN.",
"text":"The NCEP/Hydro menu contains nine sections: SPC, TPC, NCO, HPC, MPC, CPC, AWC, Hydro, and Local Analyses/Statistical Guidance. Each section is further subdivided into related products, as described below. For more information on hydro products, refer to documentation prepared by the NWS' Office of Hydrology.\n\n\nSPC\n\uf0c1\n\n\nStorm Prediction Center (SPC) Watches, Severe Weather Plots, SPC Convective Outlooks, and Fire Weather information. Severe Weather Plots are extracted from the STADTS and STAHRY text products and plotted to time-match the current display. The Severe Weather Plots data set in the NCEP/Hydro Menu can be interrogated (sampled) for more detailed information by clicking mouse Button 1 (B1) over a site.\n\n\nTPC\n\uf0c1\n\n\nContains the hurricane submenu, which comprises graphic products that display the Marine/Tropical Cyclone Advisory (TCM), the Public Tropical Cyclone Advisory (TCP), hourly forecasts, and model guidance.\n\n\nHPC\n\uf0c1\n\n\nContains 6-hour QPF (Quantitative Precipitation Forecast) data plus the submenus, described\nbelow, for Precipitation and Temps \n Weather products.\n\n\n\n\nPrecipitation\n Contains probabilities of daily precipitation, precipitation accumulation, and probabilities of daily snowfall. In addition, this submenu enables you to display QPF projections for 1 to 3 days in 6 hour increments, 4 to 5 days in 48 hour increments, and 1 to 5 days in 120 hour increments. The HPC Excessive Rainfall product consists of a contour graphic and image of the excessive rainfall for day 1 (with forecast times of 21, 24, 27, or 30 hours), and days 2 and 3 (both with forecast times of 48 and 72 hours). The HPC product will update the selected forecast cycle twice per day.\n\n\nTemps \n Weather\n Contains daily Max/Min temperature anomalies, daily heat index\nprobabilities, and pressure and frontal analysis.\n\n\n\n\nMPC\n\uf0c1\n\n\nContains the Marine Guidance submenu, which includes marine analyses and model guidance. Note that the Marine Prediction Center (MPC) is now called the Ocean Prediction Center (OPC).\n\n\nCPC\n\uf0c1\n\n\nContains threat charts and outlook grids derived from these two submenus:\n\n\n\n\nThreat Charts\n Contains drought monitoring data, daily threats assessment, and daily heat index forecasts.\n\n\nOutlook Grids\n Contains temperature and precipitation probabilities.\n\n\n\n\nAWC\n\uf0c1\n\n\nContains CCFP (Collaborative Convective Forecast Product), an aviation product. Formerly located under the Aviation option on the Upper Air menu, CCFP is a strategic forecast of convection to guide traffic managers in their system-wide approach to managing traffic. The forecast suite consists of 3 forecast maps with selectable lead times (4, 6, and 8 hours). The forecasts are issued by the Aviation Weather Center (AWC) between March 1 and October 30, eleven times per day.\n\n\nCCFP is alpha-numeric information suitable for the graphical depiction of forecast areas of significant thunderstorms. The CCFP message covers the CONUS area, and includes information on the location of thunderstorm areas, and associated information such as storm tops, coverage, confidence, and direction/speed of movement.\n\n\nNCO\n\uf0c1\n\n\nContains Precip \n Stability, Temps \n Weather, National Centers model, NGM MOS (NGM-based MOS system), and the following Sounding-derived plots submenus.\n\n\n\n\nPrecip \n Stability\n: Contains precipitation, radar, and stability products.\n\n\nTemps \n Weather\n: Contains Max/Min temperature, freezing level, weather depiction, and surface geostrophic wind and relative vorticity plots.\n\n\nNational Centers Models\n: Contains model guidance from the National Centers\n\n\nSounding-derived plots\n: Contains options to display model soundings (sometimes called \"BUFR soundings\"becausetheyarepackagedinBUFRformatfortransmission).Thesearesoundingsextracteddirectlyfromthemodel,includingalllevelsnotgeneratedfromthepressure-levelgridsusedelsewhereinthesystem.\n\n\nSoundingAvailability\nThisoptiondispla
"title":"NCEP/Hydro"
},
{
"location":"/cave/d2d-hydro/#spc",
"text":"Storm Prediction Center (SPC) Watches, Severe Weather Plots, SPC Convective Outlooks, and Fire Weather information. Severe Weather Plots are extracted from the STADTS and STAHRY text products and plotted to time-match the current display. The Severe Weather Plots data set in the NCEP/Hydro Menu can be interrogated (sampled) for more detailed information by clicking mouse Button 1 (B1) over a site.",
"title":"SPC"
},
{
"location":"/cave/d2d-hydro/#tpc",
"text":"Contains the hurricane submenu, which comprises graphic products that display the Marine/Tropical Cyclone Advisory (TCM), the Public Tropical Cyclone Advisory (TCP), hourly forecasts, and model guidance.",
"title":"TPC"
},
{
"location":"/cave/d2d-hydro/#hpc",
"text":"Contains 6-hour QPF (Quantitative Precipitation Forecast) data plus the submenus, described\nbelow, for Precipitation and Temps Weather products. Precipitation Contains probabilities of daily precipitation, precipitation accumulation, and probabilities of daily snowfall. In addition, this submenu enables you to display QPF projections for 1 to 3 days in 6 hour increments, 4 to 5 days in 48 hour increments, and 1 to 5 days in 120 hour increments. The HPC Excessive Rainfall product consists of a contour graphic and image of the excessive rainfall for day 1 (with forecast times of 21, 24, 27, or 30 hours), and days 2 and 3 (both with forecast times of 48 and 72 hours). The HPC product will update the selected forecast cycle twice per day. Temps Weather Contains daily Max/Min temperature anomalies, daily heat index\nprobabilities, and pressure and frontal analysis.",
"title":"HPC"
},
{
"location":"/cave/d2d-hydro/#mpc",
"text":"Contains the Marine Guidance submenu, which includes marine analyses and model guidance. Note that the Marine Prediction Center (MPC) is now called the Ocean Prediction Center (OPC).",
"title":"MPC"
},
{
"location":"/cave/d2d-hydro/#cpc",
"text":"Contains threat charts and outlook grids derived from these two submenus: Threat Charts Contains drought monitoring data, daily threats assessment, and daily heat index forecasts. Outlook Grids Contains temperature and precipitation probabilities.",
"title":"CPC"
},
{
"location":"/cave/d2d-hydro/#awc",
"text":"Contains CCFP (Collaborative Convective Forecast Product), an aviation product. Formerly located under the Aviation option on the Upper Air menu, CCFP is a strategic forecast of convection to guide traffic managers in their system-wide approach to managing traffic. The forecast suite consists of 3 forecast maps with selectable lead times (4, 6, and 8 hours). The forecasts are issued by the Aviation Weather Center (AWC) between March 1 and October 30, eleven times per day. CCFP is alpha-numeric information suitable for the graphical depiction of forecast areas of significant thunderstorms. The CCFP message covers the CONUS area, and includes information on the location of thunderstorm areas, and associated information such as storm tops, coverage, confidence, and direction/speed of movement.",
"title":"AWC"
},
{
"location":"/cave/d2d-hydro/#nco",
"text":"Contains Precip Stability, Temps Weather, National Centers model, NGM MOS (NGM-based MOS system), and the following Sounding-derived plots submenus. Precip Stability : Contains precipitation, radar, and stability products. Temps Weather : Contains Max/Min temperature, freezing level, weather depiction, and surface geostrophic wind and relative vorticity plots. National Centers Models : Contains model guidance from the National Centers Sounding-derived plots : Contains options to display model soundings (sometimes called \"BUFR soundings\" because they are packaged in BUFR format for transmission). These are soundings extracted directly from the model, including all levels not generated from the pressure-level grids used elsewhere in the system. Sounding Availability This option displays the sounding locations (shown with asterisks) available from the latest model run; typically these locations coincide with TAF (Terminal Aerodrome Forecast) locations. The plot will update with each model run. Because the sounding data is quite voluminous, only soundings over your State(s) scale are saved. Surface The Surface Plots, which mimic the METAR Surface Plots, are taken from the model-derived soundings and provide hourly forecast surface plots. Because you cannot see all forecast projections in a 32 frame loop (e.g., displaying the entire North American Model (NAM) or Global Forecasting System (GFS) run would require 61 frames), you will probably want to use the Time Options Tool (refer to Subsection 2.2.6.4) to view a subset of the forecast -- perhaps a continuous run of hours or every other hour for the whole run. Ceiling/Visibility The \"Ceil/Vis Plot\" shows weather (rain, frz rain, snow) on the right, a stack of three cloud layers above, and visibility below the METAR station. The cloud layers are defined as low (990mb-640mb), mid (640mb-350mb), and high ( 350mb). Each cloud layer shows a coverage circle with clear, sct, bkn, and ovc options. Next to one of the circles, there may be a cloud base. The cloud base is sent as a pressure, but is plotted in hft MSL based on a Standard Atmosphere conversion. Because the cloud layers and the cloud base are generated from separate algorithms at NCEP (National Centers for Environmental Prediction), it is possible to have broken or overcast clouds indicated but no base; alternatively, the base may be shown with a high overcast, while ignoring a mid broken layer. Also, a cloud base is reported if convective precipitation is indicated, even for only 10-20% cloud cover. As a result, one can see a cloud base associated with scattered clouds. 1 Hr and 3 Hr Precip Amt This option shows hourly amounts for NAM and 3 hour intervals for GFS at each location. Cloud Layers This option displays the amount of low, middle, and high cloud cover, each as a standard sky coverage symbol, and weather type as a weather symbol.",
"title":"NCO"
},
{
"location":"/cave/d2d-hydro/#hydro",
"text":"Contains QPE, QPF, and RFC Flash Flood Guidance submenus. Hydro Applications, such as HydroView and MPE Editor, are loaded from the Perspectives dialog (Hydro and MPE, respectively) or from the HydroApps menu in the Hydro(View) Perspective (Hydrobase, RiverPro, XDAT, Forecast Service, River Monitor, Precip Monitor, SSHP, and Dam Catalog). QPE : Makes available mosaic images of RFC-generated Quantitative Precipitation Estimator (QPE) and the Multisensor Precipitation Estimator (MPE) grids, which are displayed using a 'truncated' grid color table that shows zero values in gray to let you see the limits of the site-specified domain. These mosaic images are generated by the RFCs in 1, 6, and 24 hour cycles. The MPE grids can be displayed as local contours or images. NESDIS produces two types of Satellite Precipitation Estimates (SPE) based on GOES (Geostationary Operational Environmental Satellite) imagery series: Auto SPEs and Manual SPEs. Auto SPEs, which can be displayed directly from the QPE submenu, are produced hourly based on the most recent one-hour series of IR GOES imagery. This product is displayable on any AWIPS scale. The Auto SPE estimates are displayed in units of inches of precipitation that fell during the specified one hour period. Manual SPEs are accessible through the Manual SPE submenu. You can access the Manual SPE submenu from the QPE submenu. Generation of these products requires substantial manual intervention by NESDIS personnel; consequently, these products are generated and distributed to AWIPS at variable frequencies, as significant precipitation events warrant (i.e., their frequency is variable). The duration (or valid period) of the Manual SPEs is also variable. Whereas the duration of Auto SPEs is always one hour, the duration of the Manual SPEs ranges from 1 to 12 hours. Furthermore, although each Manual SPE product is mapped to a CONUS grid, the area of analysis is usually regional (focusing on the significant precipitation event). Apart from these important differences, the Manual SPEs are very similar to the Auto SPEs. QPF : Displays QPF, which indicate how much precipitation will occur in a particular grid. QPFs, which are issued by the RFCs, display as contours by default. However, from the pop-up menu you can convert them to image form. RFC Flash Flood Guidance : Displays County and Zone Flash Flood Guidance (FFG) grids on any scale. The area for which the data is displayed is limited, but the site system manager may configure a larger area. In addition, 1h, 3h, and 6h mosaic RFC-generated FFG grids can be displayed for both local and other RFC locations.",
"text":"Model Output Statistical (MOS) plots derived from the MOS BUFR and Text Bulletins display forecast data for GFS MOS, GFS-Extended MOS, Eta MOS, and NGM MOS. The plots are accessed by selecting NGM or GFS-LAMP/MOS forecasts under the Local Analyses/Statistical Guidance option.",
"title":"Local Analyses/Statistical Guidance"
},
{
"location":"/cave/d2d-map-resources/",
"text":"These programs are accessible though the \nMaps\n dropdown menu.\n\n\n\n\nInterstates\n\n\nInterstates and US Highways\n\n\nWarning Areas (with station identifier)\n\n\nWSR-88D Station Locations",
"text":"The \npython-awips\n package provides a data access framework for requesting grid and geometry datasets from an EDEX server.\n\n\n\n\nFor a more detailed look at the python-awips package, refer to the \nfull documentation site\n which includes a number of \nplotting examples for different data types\n.\n\n\n\n\n\n\nInstall\n\uf0c1\n\n\npip install python-awips\n\n\n\n\n\nRequirements\n\uf0c1\n\n\n\n\nPython 2.7+\n\n\nNumpy 1.7+\n\n\nShapely 1.4+\n\n\nMetPy and enum34 to run Jupyter Notebook examples\n\n\n\n\n\n\nExample\n\uf0c1\n\n\nThe simplest example requesting the RAP40 surface temperature grid from a remote EDEX server, saved to 2-dimensional Numpy arrays named \ndata\n, \nlons\n, and \nlats\n.\n\n\nfrom awips.dataaccess import DataAccessLayer\nDataAccessLayer.changeEDEXHost(\"edex-cloud.unidata.ucar.edu\")\nrequest = DataAccessLayer.newDataRequest()\ndataTypes = DataAccessLayer.getSupportedDatatypes()\nrequest.setDatatype(\"grid\")\nrequest.addLocationNames(\"RAP40\")\nrequest.setParameters(\"T\")\nrequest.setLevels(\"0.0SFC\")\ncycles = DataAccessLayer.getAvailableTimes(request, True)\ntimes = DataAccessLayer.getAvailableTimes(request)\nresponse = DataAccessLayer.getGridData(request, times[-1])\nfor grid in response:\n data = grid.getRawData()\n lons, lats = grid.getLatLonCoords()",
"text":"The simplest example requesting the RAP40 surface temperature grid from a remote EDEX server, saved to 2-dimensional Numpy arrays named data , lons , and lats . from awips.dataaccess import DataAccessLayer\nDataAccessLayer.changeEDEXHost(\"edex-cloud.unidata.ucar.edu\")\nrequest = DataAccessLayer.newDataRequest()\ndataTypes = DataAccessLayer.getSupportedDatatypes()\nrequest.setDatatype(\"grid\")\nrequest.addLocationNames(\"RAP40\")\nrequest.setParameters(\"T\")\nrequest.setLevels(\"0.0SFC\")\ncycles = DataAccessLayer.getAvailableTimes(request, True)\ntimes = DataAccessLayer.getAvailableTimes(request)\nresponse = DataAccessLayer.getGridData(request, times[-1])\nfor grid in response:\n data = grid.getRawData()\n lons, lats = grid.getLatLonCoords()",
"text":"Quick instructions on how to deploy CAVE from Eclipse.\n\n\n\n\n\n\nChange \n/etc/yum.repos.d/awips2.repo\n to \n\n\n[awips2repo]\nname=AWIPS II Repository\nbaseurl=http://www.unidata.ucar.edu/repos/yum/awips2-dev/\nenabled=1\nprotect=0\ngpgcheck=0\nproxy=_none_\n\n\n\n\n\n\n\nyum clean all \n yum groupinstall awips2-ade\n\n\nThis will install Eclipse (4.5), Java (1.8), Ant, Maven, Python 2.7 and its modules (Numpy, Matplotlib, Shapely, others). \n\n\n\n\n\n\ngit clone https://github.com/Unidata/awips2.git\n\n\nThe full list of repositories required as of release 17.1.1:\n\n\ngit clone https://github.com/Unidata/awips2.git\ngit clone https://github.com/Unidata/awips2-core.git\ngit clone https://github.com/Unidata/awips2-core-foss.git\ngit clone https://github.com/Unidata/awips2-foss.git\ngit clone https://github.com/Unidata/awips2-ncep.git\ngit clone https://github.com/Unidata/awips2-goesr.git\ngit clone https://github.com/Unidata/awips2-nws.git\ngit clone https://github.com/Unidata/awips2-gsd.git\ngit clone https://github.com/Unidata/awips2-drawing.git\ngit clone https://github.com/Unidata/awips2-cimss.git\n\n\n\n\n\n\n\nRun \n/awips2/eclipse/eclipse.sh\n\n\n\n\n\n\nPreferences \n Java \n\n\nSet to \n/awips2/java\n\n\n\n\n\n\nPreferences \n PyDev \n Python Interpreter\n\n\nSet to \n/awips2/python/bin/python\n (should be resolved by Auto-Config)\n\n\n\n\n\n\nFile \n Import \n General \n Existing Projects Into Workspace\n\n\nImport all of the git cloned project folders \nEXCEPT\n for the main (first) \ngithub.com/Unidata/awips2.git\n directory (which should be \n~/awips2\n).\n\n\nYou'll want to import \n~/awips2\n in three parts to ensure a clean and error-free Eclipse build:\n\n\n\n\nImport \nawips2/cave\n \n Select All Projects \n Finish\n\n\nImport \nawips2/edexOsgi\n \n Select All Projects \n Finish\n\n\nImport \nawips2/Radar\n \n Select All Projects \n Finish\n \n The \nRadar\n folder contains the EDEX Radar Server plugins. Though the Unidata release does not build or use the radar server, the common libraries are required for other AWIPS radar processing and visualization plugins.\n\n\n\n\nNow import all other repositories fully: \n\n\nSelect \nawips2-core\n, \nawips2-core-foss\n, \nawips2-foss\n, \nawips2-ncep\n, etc. \n Select All Projects \n Finish \n\n\n\n\n\n\nProject \n Clean\n\n\nRun a clean build and ensure no errors are reported. \n\n\n\n\n\n\n\n\n\n\nRun \ncom.raytheon.viz.product.awips/developer.product\n\n\nDouble-click the \ndeveloper.product\n file to open the Product View in Eclipse. Select \nOverview\n \n \nSynchronize\n and then right-click the file in the left-side package explorer:\n\n\nSelect \nRun As\n \n \nEclipse Application\n to launch CAVE in the development environment. \n\n\nSelect \nDebug\n \n \nEclipse Application\n to launch CAVE in in debug mode.",
"title":"AWIPS Development Environment (ADE)"
},
{
"location":"/dev/build-nsharp-macos/",
"text":"A little known fact in the world of AWIPS(II) is just how dependent the system still is on NAWIPS-GEMPAK. The entire National Centers Perspective is dependent on pre-built shared object files for 64-bit Linux, which means that all of the D2D plugins which extend NSHARP (for bufr obs, NPP profiles, forecast models, etc.) also depend on these libraries.\n\n\nThis dependency has prevented use of the NSHARP plugin in the first release (15.1.1) of the \nOS X CAVE client\n. These are the steps taken to build NSHARP and GEMPAK libraries for OS X AWIPS 16.2.2.\n\n\nYou will need the \nhttps://github.com/Unidata/awips2-gemlibs\n repository on your Mac, as well as gcc and gfortran (from XCode). Pay attention to any version-specific include path or linked files, such as \n/usr/local/Cellar/gcc/4.9.2_1/lib/gcc/4.9/\n, always account for the correct versions and locations on your own system.\n\n\nNSHARP pre-built libraries\n\uf0c1\n\n\n\n\nlibbignsharp.dylib\n\n\n\n\nUsing the script below, the NSHARP dynamic library is built from C and FORTRAN source files (and their required include files supplied by the \nawips2-gemlibs\n repository, and as linked against \n$GEMINC\n, meaning that GEMPAK for OS X must be built and installed).\n\n\ngit clone https://github.com/Unidata/awips2-gemlibs.git\ncd awips2-gemlibs/nsharp/\n\n\n\nAn optional step, which can be performed in a separate script or within the build script below, is to create \nld-style\n *.a files in \n$OS_LIB\n which can then be referenced with \n-l\n flags (e.g. \n-lgemlib\n):\n\n\nlibs=(snlist sflist nxmlib gemlib gplt cgemlib rsl device xwp xw ps gn nsharp netcdf textlib)\nfor file in ${libs[@]}\ndo\n if [ ! -f $OS_LIB/lib$file.a ]; then\n echo \"$OS_LIB/lib$file.a does not exist\"\n if [ -f $OS_LIB/$file.a ]; then\n cp $OS_LIB/$file.a $OS_LIB/lib$file.a\n echo \"copied OS_LIB/$file.a to OS_LIB/lib$file.a for linking\"\n fi\n fi\ndone\n\n\n\nBuild libbignsharp.dylib with the following script (Note the GEMPAK includes and links \n-I$NSHARP\n, \n-I$GEMPAK/include\n, \n-L$OS_LIB\n, etc.).\n\n\n#!/bin/bash\ncd ~/awips2-gemlibs/nsharp/\n. $NAWIPS/Gemenviron.profile\nCC=gcc\nFC=gfortran\n\nexport NSHARP=$GEMPAK/source/programs/gui/nsharp\nexport NWX=$GEMPAK/source/programs/gui/nwx\n\nmyLibs=\"$OS_LIB/ginitp_alt.o $OS_LIB/gendp_alt.o\"\n\nmyCflags=\"$CFLAGS -I. -I./Sndglib -I$NSHARP -I$GEMPAK/include -I$OS_INC -I$NWX \\\n-I/opt/X11/include/X11 -I/usr/include/Xm -I/opt/local/include -I/usr/include/malloc -Wcomment -Wno-return-type -Wincompatible-pointer-types -DUNDERSCORE -fPIC -DDEBUG -c\"\n\nmyFflags=\"-I. -I$OS_INC -I$GEMPAK/include -I$NSHARP -fPIC -g -c -fno-second-underscore -fmax-errors=200 -std=f95\"\n\nmyLinkflags=\"-L/usr/local/Cellar/gcc/4.9.2_1/lib/gcc/4.9/ -L/opt/local/lib -L$OS_LIB -L. -L./Sndglib -L/usr/X11R6/lib \\\n-shared -Wl -Wcomment -Wincompatible-pointer-types -Wimplicit-function-declaration -Wno-return-type,-install_name,libbignsharp.dylib -o libbignsharp.dylib\"\n\nmyLibsInc=\"$OS_LIB/ginitp_alt.o $OS_LIB/gendp_alt.o $OS_LIB/libnxmlib.a $OS_LIB/libsnlist.a \\\n $OS_LIB/libsflist.a $OS_LIB/libgemlib.a $OS_LIB/libcgemlib.a $OS_LIB/libgplt.a $OS_LIB/libdevice.a \\\n $OS_LIB/libxwp.a $OS_LIB/libxw.a $OS_LIB/libps.a $OS_LIB/libgn.a $OS_LIB/libcgemlib.a $OS_LIB/libgemlib.a \\\n $OS_LIB/libnetcdf.a $OS_LIB/libtextlib.a $OS_LIB/libxml2.a $OS_LIB/libxslt.a \\\n $OS_LIB/libgemlib.a $OS_LIB/libcgemlib.a $OS_LIB/librsl.a $OS_LIB/libbz2.a\"\n\nmyLinktail=\"-I$OS_INC \\\n -I$GEMPAK/include -I$NWX -I$NSHARP -I. -I./Sndglib -I/opt/X11/include/X11 -I/usr/include -I/usr/include/Xm -I/opt/local/include/ -I/opt/local/include -lhdf5 -lgfortran -ljasper -lpng -liconv -lc -lXt -lX11 -lz -lm -lXm\"\n\n$CC$myCflags*.cSndglib/*.c\n$FC$myFflags*.f\n$CC$myLinkflags*.o$myLibsInc$myLinktail\n\ncplibbignsharp.dylib~/awips2-ncep/viz/gov.noaa.nws.ncep.ui.nsharp.macosx/\n\n\n\nGEMPAKpre-builtlibraries\n\uf0c1\n\n\n\n\nlibgempak.dylib\n\n\n\n\nlibgempak.dylibisbuiltinasimilarwayaslibbignsharp.dylib:\n\n\n#!/bin/bash\ncd~/aw
"text":"libbignsharp.dylib Using the script below, the NSHARP dynamic library is built from C and FORTRAN source files (and their required include files supplied by the awips2-gemlibs repository, and as linked against $GEMINC , meaning that GEMPAK for OS X must be built and installed). git clone https://github.com/Unidata/awips2-gemlibs.git\ncd awips2-gemlibs/nsharp/ An optional step, which can be performed in a separate script or within the build script below, is to create ld-style *.a files in $OS_LIB which can then be referenced with -l flags (e.g. -lgemlib ): libs=(snlist sflist nxmlib gemlib gplt cgemlib rsl device xwp xw ps gn nsharp netcdf textlib)\nfor file in ${libs[@]}\ndo\n if [ ! -f $OS_LIB/lib$file.a ]; then\n echo \"$OS_LIB/lib$file.a does not exist\"\n if [ -f $OS_LIB/$file.a ]; then\n cp $OS_LIB/$file.a $OS_LIB/lib$file.a\n echo \"copied OS_LIB/$file.a to OS_LIB/lib$file.a for linking\"\n fi\n fi\ndone Build libbignsharp.dylib with the following script (Note the GEMPAK includes and links -I$NSHARP , -I$GEMPAK/include , -L$OS_LIB , etc.). #!/bin/bash\ncd ~/awips2-gemlibs/nsharp/\n. $NAWIPS/Gemenviron.profile\nCC=gcc\nFC=gfortran\n\nexport NSHARP=$GEMPAK/source/programs/gui/nsharp\nexport NWX=$GEMPAK/source/programs/gui/nwx\n\nmyLibs=\"$OS_LIB/ginitp_alt.o $OS_LIB/gendp_alt.o\"\n\nmyCflags=\"$CFLAGS -I. -I./Sndglib -I$NSHARP -I$GEMPAK/include -I$OS_INC -I$NWX \\\n-I/opt/X11/include/X11 -I/usr/include/Xm -I/opt/local/include -I/usr/include/malloc -Wcomment -Wno-return-type -Wincompatible-pointer-types -DUNDERSCORE -fPIC -DDEBUG -c\"\n\nmyFflags=\"-I. -I$OS_INC -I$GEMPAK/include -I$NSHARP -fPIC -g -c -fno-second-underscore -fmax-errors=200 -std=f95\"\n\nmyLinkflags=\"-L/usr/local/Cellar/gcc/4.9.2_1/lib/gcc/4.9/ -L/opt/local/lib -L$OS_LIB -L. -L./Sndglib -L/usr/X11R6/lib \\\n-shared -Wl -Wcomment -Wincompatible-pointer-types -Wimplicit-function-declaration -Wno-return-type,-install_name,libbignsharp.dylib -o libbignsharp.dylib\"\n\nmyLibsInc=\"$OS_LIB/ginitp_alt.o $OS_LIB/gendp_alt.o $OS_LIB/libnxmlib.a $OS_LIB/libsnlist.a \\\n $OS_LIB/libsflist.a $OS_LIB/libgemlib.a $OS_LIB/libcgemlib.a $OS_LIB/libgplt.a $OS_LIB/libdevice.a \\\n $OS_LIB/libxwp.a $OS_LIB/libxw.a $OS_LIB/libps.a $OS_LIB/libgn.a $OS_LIB/libcgemlib.a $OS_LIB/libgemlib.a \\\n $OS_LIB/libnetcdf.a $OS_LIB/libtextlib.a $OS_LIB/libxml2.a $OS_LIB/libxslt.a \\\n $OS_LIB/libgemlib.a $OS_LIB/libcgemlib.a $OS_LIB/librsl.a $OS_LIB/libbz2.a\"\n\nmyLinktail=\"-I$OS_INC \\\n -I$GEMPAK/include -I$NWX -I$NSHARP -I. -I./Sndglib -I/opt/X11/include/X11 -I/usr/include -I/usr/include/Xm -I/opt/local/include/ -I/opt/local/include -lhdf5 -lgfortran -ljasper -lpng -liconv -lc -lXt -lX11 -lz -lm -lXm\"\n\n$CC $myCflags *.c Sndglib/*.c\n$FC $myFflags *.f\n$CC $myLinkflags *.o $myLibsInc $myLinktail\n\ncp libbignsharp.dylib ~/awips2-ncep/viz/gov.noaa.nws.ncep.ui.nsharp.macosx/",
"text":"ACARS - Aircraft Communications Addressing and Reporting System AEV - AFOS-Era Verification AFOS - Automation of Field Operations and Services AGL - above ground level AI - AWIPS Identifier AMSU - Advanced Microwave Sounding Unit ARD - AWIPS Remote Display ASL - Above Sea Level ASOS - Automated Surface Observing System ASR - Airport Surveillance Radar ATMS - Advanced Technology Microwave Sounder AvnFPS - Aviation Forecast Preparation System AVP - AWIPS Verification Program AWC - Aviation Weather Center AWIPS - Advanced Weather Interactive Processing System",
"title":"A"
},
{
"location":"/appendix/appendix-acronyms/#b",
"text":"BGAN - Broadboand Global Area Network BUFR - Binary Universal Form for the Representation of meteorological data",
"title":"B"
},
{
"location":"/appendix/appendix-acronyms/#c",
"text":"CAPE - Convective Available Potential Energy CAVE - Common AWIPS Visualization Environment CC - Correlation Coefficient CCF - Coded Cities Forecast CCFP - Collaborative Convective Forecast Product CCL - Convective Condensation Level CDP - Cell Display Parameters CFC - Clutter Filter Control CGI - Common Gateway Interface CIN - Convective Inhibition CITR - Commerce Information Technology Requirement CONUS - Conterminous/Contiguous/Continental United States COOP - Continuity Of Operations Planning COTS - commercial off-the-shelf CrIMSS - Cross-track Infrared and Microwave Sounder Suite CrIS - Cross-track Infrared Sounder CWA - County Warning Area CWSU - Center Weather Service Unit CZ - Composite Reflectivity",
"title":"C"
},
{
"location":"/appendix/appendix-acronyms/#d",
"text":"D2D - Display 2 Dimensions DFM - Digital Forecast Matrix DMD - Digital Mesocyclone Display DMS - Data Monitoring System DOC - Department of Commerce DPA - Digital Precipitation Array",
"title":"D"
},
{
"location":"/appendix/appendix-acronyms/#e",
"text":"ECMWF - European Centre for Medium-Range Forecasts EDEX - Enterprise Data EXchange EMC - Environmental Modeling Center EL - Equilibrium Level ESA - Electronic Systems Analyst ESRL - Earth System Research Laboratory",
"text":"GFE - Graphical Forecast Editor GFS - Global Forecasting Systems GHG - Graphical Hazards Generator GIS - Geographic Information Systems GMT - Greenwich Mean Time GOES - Geostationary Operational Environmental Satellite GSD - Global System Division",
"title":"G"
},
{
"location":"/appendix/appendix-acronyms/#h",
"text":"HC - Hydrometeor Classification HI - Hail Index HM - Hydromet HPC - Hydrologic Precipitation Center HWR - Hourly Weather Roundup",
"title":"H"
},
{
"location":"/appendix/appendix-acronyms/#i",
"text":"ICAO - International Civil Aviation Organization IFP - Interactive Forecast Program IFPS - Interactive Forecast Preparation System IHFS - Integrated Hydrologic Forecast System IMET - Incident Meteorologist IR - infrared ISS - Incident Support Specialist IST - Interactive Skew-T",
"title":"I"
},
{
"location":"/appendix/appendix-acronyms/#j",
"text":"JMS - Java Messaging System",
"title":"J"
},
{
"location":"/appendix/appendix-acronyms/#k",
"text":"KDP - Specific Differential Phase KML - Keyhole Markup Language KMZ - KML zipped (compressed).",
"title":"K"
},
{
"location":"/appendix/appendix-acronyms/#l",
"text":"LAC - Listening Area Code LAMP - Localized Aviation MOS Program LAN - Local Area Network LAPS - Local Analysis and Prediction System LARC - Local Automatic Remote Collector LCL - Lifting Condensation Level LDAD - Local Data Acquisition and Dissemination LFC - Level of Free Convection LSR - Local Storm Report",
"title":"L"
},
{
"location":"/appendix/appendix-acronyms/#m",
"text":"MAPS - Mesoscale Analysis and Prediction System mb - millibar; pressure MDCRS - Meteorological Data Collection and Receiving System MDL - Meteorological Development Laboratory MDP - Mesocyclone Display Parameters MDPI - Microburst-Day Potential Index MEF - Manually Entered Forecast METAR - Meteorological Aviation Report MHS - message handling system ML - Melting Layer MND - Mass News Dissemination MOS - Model Output Statistics MPC - Marine Prediction Center MPE - Multisensor Precipitation Estimator MRD - Message Reference Descriptor MRU - Meso Rapid Update MSAS - MAPS Surface Assimilation System MSL - Mean Sea Level",
"title":"M"
},
{
"location":"/appendix/appendix-acronyms/#n",
"text":"NAM - North American Mesoscale model NCEP - National Centers for Environmental Prediction NCF - Network Control Facility NDFD - National Digital Forecast Database NE-PAC - Northeastern Pacific NESDIS - National Environmental Satellite, Data and Information Service NH - Northern Hemisphere nMi - nautical miles NOAA - National Oceanic and Atmospheric Administration NPN - NOAA Profiler Network NPP - Suomi National Polar-orbiting Partnership NUCAPS - NOAA Unique CrIS/ATMS Processing Systems NWP - Numerical Weather Prediction NWR - NOAA Weather Radio NWS - National Weather Service NWRWAVES - NOAA Weather Radio With All-Hazards VTEC Enhanced Software NWSRFS - National Weather Service River Forecast System NWWS - NOAA Weather Wire Service",
"title":"N"
},
{
"location":"/appendix/appendix-acronyms/#o",
"text":"OCP - Ocean Prediction Center OH - Office of Hydrology OPC - Ocean Prediction Center ORPG - Open Radar Products Generator OSD - One Hour Snow Depth OSW - One Hour Snow Water OTR - One Time Request",
"title":"O"
},
{
"location":"/appendix/appendix-acronyms/#p",
"text":"PID - Product Identification PIL - Product Inventory List PIREP - Pilot Weather Report POES - Polar Operational Environmental Satellite POSH - Probability of Severe Hail POH - Probability of Hail POP - Probability of Precipitation PQPF - Probabilistic QPF PRF - Pulse Repetition Frequency",
"title":"P"
},
{
"location":"/appendix/appendix-acronyms/#q",
"text":"QC - quality control QCMS - Quality Control and Monitoring System QPE - Quantitative Precipitation Estimator QPF - Quantitative Precipitation Forecast QPS - Quantitative Precipitation Summary",
"title":"Q"
},
{
"location":"/appendix/appendix-acronyms/#r",
"text":"RAOB - Radiosonde Observation RAP - Rapid Refresh (Replaced RUC) RCM - Radar Coded Message RER - Record Report RFC - River Forecast Center RGB - Red, Green, Blue RHI - Range Height Indicator RMR - Radar Multiple Request ROSA - Remote Observing System Automation RPG - Radar Product Generator RPS - routine product set RTD - Requirements Traceability Document; Routine, Delayed RTMA - Real Time Mesoscale Analysts RUC - Rapid Update Cycle (Replaced by RAP)",
"title":"R"
},
{
"location":"/appendix/appendix-acronyms/#s",
"text":"SAFESEAS - System on AWIPS for Forecasting and Evaluation of Seas and Lakes SBN - Satellite Broadcast Network SCAN - System for Convection Analysis and Nowcasting SCD - Supplementary Climatological Data SCID - Storm Cell Identification Display SCP - Satellite Cloud Product SCTI - SCAN CWA Threat Index SDC - State Distribution Circuit SNOW - System for Nowcasting Of Winter Weather SOO - Science and Operations Officer SPC - Storm Prediction Center SPE - Satellite Precipitation Estimate SREF - Short Range Ensemble Forecast SRG - Supplemental Product Generator SRM - Storm Relative Motion SSD - Storm-Total Snow Depth SSM/I - Special Sensor Microwave/Imager SSW - Storm-Total Snow Water STI - Storm Track Information Suomi NPP - Suomi National Polar-orbiting Partnership SW - Spectrum Width SWEAT Index - Severe Weather Threat Index SWP - Severe Weather Probability",
"title":"S"
},
{
"location":"/appendix/appendix-acronyms/#t",
"text":"TAF - Terminal Aerodrome Forecast (international code) TAFB - Tropical Analysis and Forecast Branch TCM - Marine/Tropical Cyclone Advisory TCP - Public Tropical Cyclone Advisory TDWR - Terminal Doppler Weather Radio TE-PAC - Tropical Pacific TMI - Text Message Intercept TRU - TVS Rapid Update TT - Total Totals TVS - Tornado Vortex Signature TWB - Transcribed Weather Broadcasts",
"title":"T"
},
{
"location":"/appendix/appendix-acronyms/#u",
"text":"UGC - Universal Geographic Code ULR - User Selectable Layer Reflectivity URL - Universal Resource Locator USD - User Selectable Snow Depth USW - User Selectable Snow Water UTC - Coordinated Universal Time",
"title":"U"
},
{
"location":"/appendix/appendix-acronyms/#v",
"text":"VAD - Velocity Azimuth Display VCP - volume coverage pattern VIIR - Visible Infrared Imager Radiometer Suite VIL - Vertically Integrated Liquid VTEC - Valid Time and Event Code VWP - VAD Wind Profile",
"title":"V"
},
{
"location":"/appendix/appendix-acronyms/#w",
"text":"W-ATL - Western Atlantic WFO - Weather Forecast Office WINDEX - Wind Index WMO - World Meteorological Organization WSFO - Weather Service Forecast Office WSO - Weather Service Office WSOM - Weather Service Operations Manual WSR-88D - Weather Surveillance Radar-1988 Doppler WWA - Watch Warning Advisory WV - water vapor",
"text":"COTS and FOSS used in AWIPS\n\n\n\n\n\n\n\n\nComponent\n\n\nVersion\n\n\nDescription\n\n\n\n\n\n\n\n\n\n\nActiveMQ\n\n\n5.3.0\n\n\nJMS (still used by AlertViz and internally in parts of Camel)\n\n\n\n\n\n\nApache Batik\n\n\n1.6\n\n\nBatik is a Java-based toolkit for applications or applets that want to use images in the Scalable Vector Graphics (SVG) format for various purposes, such as display, generation or manipulation.\n\n\n\n\n\n\nApache MINA\n\n\n1.1.7\n\n\nNetwork application framework\n\n\n\n\n\n\nApache WSS4J\n\n\n1.6.5\n\n\nWeb Services Security\n\n\n\n\n\n\nAnt\n\n\n1.7.1\n\n\nJava Build Tool\n\n\n\n\n\n\nAnt-Contrib\n\n\n1.0b3\n\n\nAdditional useful tasks and types for Ant\n\n\n\n\n\n\nAntlr\n\n\n2.7.6\n\n\nParser generator\n\n\n\n\n\n\nAtomikos TransactionEssentials\n\n\n3.6.2\n\n\nTransaction management system\n\n\n\n\n\n\nBitstream Vera Fonts\n\n\n1.10\n\n\nFont library from Gnome\n\n\n\n\n\n\nbzip2\n\n\nnone\n\n\nStream compression algorithm\n\n\n\n\n\n\nC3p0\n\n\n0.9.1\n\n\nc3p0 is an easy-to-use library for making traditional JDBC drivers \"enterprise-ready\"byaugmentingthemwithfunctionalitydefinedbythejdbc3specandtheoptionalextensionstojdbc2.\n\n\n\n\n\n\nCamel\n\n\n2.4\n\n\nEnterpriseServiceBus\n\n\n\n\n\n\ncglib\n\n\n2.2\n\n\nByteCodeGenerationLibraryishighlevelAPItogenerateandtransformJAVAbytecode.\n\n\n\n\n\n\nCherryPy\n\n\n3.1.2\n\n\nObject-orientedHTTPframework\n\n\n\n\n\n\ncommons-beanutils\n\n\n1.8.3\n\n\nApacheCommonLibraries\n\n\n\n\n\n\ncommons-codec\n\n\n1.4.1\n\n\nApacheCommonLibraries\n\n\n\n\n\n\ncommons-collection\n\n\n3.2\n\n\nApacheCommonLibraries\n\n\n\n\n\n\ncommons-configuration\n\n\n1.6\n\n\nApacheCommonLibraries\n\n\n\n\n\n\nCommons-cli\n\n\n1.2\n\n\nApacheCommonLibraries\n\n\n\n\n\n\ncommons-digester\n\n\n1.8.1\n\n\nApacheCommonLibraries\n\n\n\n\n\n\ncommons-cxf\n\n\n2.5\n\n\nApacheCommonLibraries\n\n\n\n\n\n\ncommons-httpclient\n\n\n3.1\n\n\nApacheCommonLibraries\n\n\n\n\n\n\ncommons-lang\n\n\n2.3\n\n\nApacheCommonLibraries\n\n\n\n\n\n\ncommons-logging\n\n\n1.1.1\n\n\nApacheCommonLibraries\n\n\n\n\n\n\ncommons-management\n\n\n1.0\n\n\nApacheCommonLibraries\n\n\n\n\n\n\ncommons-pool\n\n\n1.3\n\n\nApacheCommonLibraries\n\n\n\n\n\n\ncommons-validator\n\n\n1.2\n\n\nApacheCommonLibraries\n\n\n\n\n\n\ndom4j\n\n\n1.6.1\n\n\nAnopensourcelibraryforworkingwithXML,XPath,andXSLTontheJavaplatformusingtheJavaCollectionsFramework\n\n\n\n\n\n\ndwr(directwebremoting)Getahead\n\n\n1.1.3\n\n\nJavaopensourcelibrary\n\n\n\n\n\n\nEclipse\n\n\n3.6.1\n\n\nJavaIDE\n\n\n\n\n\n\nEclipseCDT\n\n\n5.0.2\n\n\nC/C++IDEforEclipse\n\n\n\n\n\n\nehcache\n\n\n1.3.0\n\n\nCachingSupport\n\n\n\n\n\n\nGEOS\n\n\n3.0.2\n\n\nGeometryEngine,RequiredforPostGIS\n\n\n\n\n\n\nGeoToolsJavaAPI\n\n\n2.6.4\n\n\nJavaAPIforManipulationofGeospatialData\n\n\n\n\n\n\nGeronimo-jms\n\n\n1.1spec1.1.1\n\n\nServerruntimeframework\n\n\n\n\n\n\nGRIBJava\n\n\n8.0\n\n\nGribJavaDecoder\n\n\n\n\n\n\nh5py\n\n\n1.3.0\n\n\nHDF5forPython\n\n\n\n\n\n\nhdf5\n\n\n1.8.4-patch1\n\n\nCoreHDF5APIs\n\n\n\n\n\n\nhdf5\n\n\n2.5\n\n\nCoreHDF5APIs\n\n\n\n\n\n\nHibernate\n\n\n3.5.0\n\n\nDataAccessLayer\n\n\n\n\n\n\nIzPack\n\n\n4.2.0\n\n\nInstallercreatorforEDEX\n\n\n\n\n\n\nJAI\n\n\n1.1.3\n\n\nJavaAPIforImageManipulation\n\n\n\n\n\n\nJAI\u2013ImageI/O\n\n\n1.1\n\n\nPlug-insforJAI\n\n\n\n\n\n\nJasper\n\n\n1.900.1\n\n\nJPEG-2000codec\n\n\n\n\n\n\nJava\n\n\n1.6u46\n\n\nKitforboth32-bitand64-bit\n\n\n\n\n\n\njavax.mail\n\n\n1.4.3\n\n\nmailmodelingclasses\n\n\n\n\n\n\njavax.measure\n\n\n1.0-beta-2\n\n\nStrongtypesformeasurements\n\n\n\n\n\n\njavax.persistence\n\n\n1.0.0\n\n\npersistenceclassesandinterfaces\n\n\n\n\n\n\njavax.vecmath\n\n\n1.3.1\n\n\nCoordinatesandvectors\n\n\n\n\n\n\nJep\n\n\n2.3+\n\n\nJavaPythoninterface\n\n\n\n\n\n\njetty\n\n\n7.2.2\n\n\nJettyprovidesanHTTPserver,HTTPclient,andjavax.servletcontainer\n\n\n\n\n\n\njGrapht\n\n\n0.6.0\n\n\nJGraphTisafreeJavagraphlibraryth
