From 7ffe21faf4361fa25570ed99c8f93dfa7c17e426 Mon Sep 17 00:00:00 2001
From: srcarter3 <srcarter3@users.noreply.github.com>
Date: Tue, 11 Jan 2022 18:04:46 +0000
Subject: [PATCH] deploy: 523a2b26e67d5f2039af44e4123ca7b48572d818

---
 install/install-cave/index.html |  4 +-
 install/install-edex/index.html |  2 +-
 search/search_index.json        | 10 ++---
 sitemap.xml                     | 78 ++++++++++++++++-----------------
 4 files changed, 47 insertions(+), 47 deletions(-)

diff --git a/install/install-cave/index.html b/install/install-cave/index.html
index b8621ade4e..fa345aa9be 100644
--- a/install/install-cave/index.html
+++ b/install/install-cave/index.html
@@ -1188,7 +1188,7 @@
 <hr />
 <h2 id="latest-cave-versions">Latest CAVE Versions<a class="headerlink" href="#latest-cave-versions" title="Permanent link"></a></h2>
 <ul>
-<li><a href="#linux"><strong>Linux: 18.2.1-3</strong></a></li>
+<li><a href="#linux"><strong>Linux: 18.2.1-4</strong></a></li>
 <li><a href="#windows"><strong>Windows: 18.2.1-3</strong></a></li>
 <li><a href="#macos"><strong>Mac: 18.2.1-3</strong></a></li>
 </ul>
@@ -1219,7 +1219,7 @@
 </ul>
 <hr />
 <h2 id="linux">Linux <i class="fa fa-linux"></i><a class="headerlink" href="#linux" title="Permanent link"></a></h2>
-<p><strong>Latest Version: 18.2.1-3</strong></p>
+<p><strong>Latest Version: 18.2.1-4</strong></p>
 <h3 id="system-requirements">System Requirements<a class="headerlink" href="#system-requirements" title="Permanent link"></a></h3>
 <ul>
 <li>64 bit CentOS/Red Hat 7</li>
diff --git a/install/install-edex/index.html b/install/install-edex/index.html
index 77a995d4c1..7a921dd727 100644
--- a/install/install-edex/index.html
+++ b/install/install-edex/index.html
@@ -1173,7 +1173,7 @@
 <p>EDEX is the <strong>E</strong>nvironmental <strong>D</strong>ata <strong>Ex</strong>change system that represents the backend server for AWIPS.  EDEX is only supported for Linux systems: CentOS and RHEL, and ideally, it should be on its own dedicated machine.  It requires administrator priviledges to make root-level changes. EDEX can run on a single machine or be spread across multiple machines.  To learn more about that please look at <a href="../../edex/distributed-computing/">Distributed EDEX, Installing Across Multiple Machines</a></p>
 <hr />
 <h2 id="latest-version">Latest Version<a class="headerlink" href="#latest-version" title="Permanent link"></a></h2>
-<p><strong>18.2.1-3</strong></p>
+<p><strong>18.2.1-4</strong></p>
 <p><a href="https://www.unidata.ucar.edu/blogs/news/tags/awips-release"><strong>View release notes</strong></a></p>
 <hr />
 <h2 id="system-requirements">System requirements<a class="headerlink" href="#system-requirements" title="Permanent link"></a></h2>
diff --git a/search/search_index.json b/search/search_index.json
index 95e2b26352..4c4edd0abb 100644
--- a/search/search_index.json
+++ b/search/search_index.json
@@ -87,7 +87,7 @@
         },
         {
             "location": "/install/install-cave/",
-            "text": "Install CAVE\n\uf0c1\n\n\nCAVE is the \nC\nommon \nA\nWIPS \nV\nisualization \nE\nnvironment that is used for rendering and analyzing data for AWIPS.  Unidata supports CAVE to work on three platforms: \nCentos (Redhat) Linux\n, \nWindows\n, and \nmacOS\n.  The installer may require administrator priviledges to install and may require other system changes (environment variables, etc) as well.\n\n\n\n\nLatest CAVE Versions\n\uf0c1\n\n\n\n\nLinux: 18.2.1-3\n\n\nWindows: 18.2.1-3\n\n\nMac: 18.2.1-3\n\n\n\n\nView release notes\n\n\n\n\nGeneral Requirements\n\uf0c1\n\n\nRegardless of what Operating System CAVE is running on, these general requirements are recommended in order for CAVE to perform optimally:\n\n\n\n\n\n\nLocal machine\n\n\n\n\nRunning CAVE via X11 forwarding or ssh tunneling is \nnot\n supported. Using a \nVNC connection is the only remote option\n, and may result in worse performance than running locally.\n\n\n\n\n\n\n\n\nJava 1.8\n\n\n\n\nOpenGL 2.0 Compatible Devices\n\n\nAt least 4GB RAM\n\n\nAt least 2GB Disk Space for Caching\n\n\nNVIDIA Graphics Card\n\n\n\n\nLatest NVIDIA Driver\n\n\n\n\nWhile other graphics cards \nmay\n work, NVIDIA Quadro graphics card is recommended for full visualization capability\n\n\n\n\n\n\n\n\n\n\nLinux \n\uf0c1\n\n\nLatest Version: 18.2.1-3\n\n\nSystem Requirements\n\uf0c1\n\n\n\n\n64 bit CentOS/Red Hat 7\n\n\n\n\nDownload and Installation Instructions\n\uf0c1\n\n\n\n\nDownload the following installer: \nawips_install.sh\n \n\n\nIn a terminal, go to the download directory \n\n\nMake the installer an executable by running: \nchmod 755 awips_install.sh\n\n\nRun the installer: \nsudo ./awips_install.sh --cave\n\n\nThis will install the application in \n/awips2/cave/\n and set the local cache to \n~/caveData/\n\n\n\n\n\n\n\n\nRun CAVE\n\uf0c1\n\n\nTo run CAVE either:\n\n\n\n\nUse the terminal and type the command \ncave\n\n\nFind the application in the Linux Desktop menu: Applications > Internet > AWIPS CAVE\n\n\n\n\n\n\nWindows \n\uf0c1\n\n\nLatest Version: 18.2.1-3\n\n\nFor Windows, Unidata offers two installation options: a \nLinux Virtual Machine\n, or a \nDirect Windows Installation\n.\n\n\nCurrently, the \nvirtual machine (VM)\n is the recommended form of install for those who do not have administrative priviledges on the machine, or beginners who want a simpler installation process.  \n\n\n\n\nAt the moment, the VM option may not render all products in CAVE (ex. RGB composites of satellite imagery)\n\n\n\n\nThe \ndirect installation method\n is recommended for those who have administrative priviledges and a little bit of experience installing more software.\n\n\nMethod 1: Linux Virtual Machine\n\uf0c1\n\n\nThis method is recommended for beginners, or those with less computer knowledge as it is a very simple installation, however at this time, some CAVE functionality may be missing (ex: rendering RGB satellite images).\n\n\nSystem Requirements\n\uf0c1\n\n\n\n\nVMWare Workstation Player\n must be installed (free software)\n\n\n\n\nDownload and Installation Instructions\n\uf0c1\n\n\n\n\nDownload the zipped file containing the virtual machine: \nunidata_cave.zip\n \n\n\nUnzip the folder by right-clicking and selecting \"Extract All\".  All files will be extracted into a new folder.\n\n\nOpen VMWare Player and go to \nPlayer\n > \nFile...\n > \nOpen\n and locate the folder that was created from the downloaded zipped file.  Select the file called \n\"CentOS 7 - Unidata CAVE 18-1-1.vmx\"\n.\n\n\nRun this new VM option.  If it asks if it's been moved or copied, select \n\"I Copied It\"\n.\n\n\nThere will be a user in the Linux machine named \"awips\" and the password is \"awips\"\n\n\nThe root password is \"unidataAWIPS\" if ever needed\n\n\n\n\n\n\n\n\nRun CAVE\n\uf0c1\n\n\nOnce inside the VM, to run CAVE either:\n\n\n\n\nUse the desktop icon \n\n\nUse the terminal and type the command \ncave\n\n\nFind the application in the Linux Desktop menu: Applications > Internet > AWIPS CAVE\n\n\n\n\nMethod 2: Direct Windows Install\n\uf0c1\n\n\nThis method is recommended for personal use and requires Administrative priviledges.  It should enable full CAVE capability, but it is a bit lengthy and might take about 20 minutes or so to complete.\n\nFor additional assistance we have created an \ninstallation video\n that walks through the steps below.\n\n\n\n\nIt is important to use the exact versions of software that we link to or specify in our instructions.  Deviations may cause installation problems or failures.\n\n\n\n\nSystem Requirements\n\uf0c1\n\n\n\n\n64-bit Miniconda3 (Python3.7 - 4.8.2)\n\n\nPython3 (comes with Miniconda installation)\n\n\n64-bit Java JDK 1.8 (1.8_181)\n\n\n64-bit Visual C++ Build Tools 2015 and 2019\n\n\nNumpy (1.15.1)\n\n\nJep (3.8.2)\n\n\nUser Variable PATH must have miniconda3 location\n\n\nUser Variables PYTHONHOME and PYTHONPATH must be defined\n\n\nSystem Variable JAVA_HOME must be defined\n\n\n\n\nDownload and Installation Instructions\n\uf0c1\n\n\n\n\nDownload and install 64-bit \nMiniconda Python3.7 version 4.8.2 for Windows\n\n\nAllow\n Miniconda3 to set \nPATH\n and other environment variables\n\n\nRegister\n miniconda as the default python\n\n\n\n\n\n\n\nDownload and install the 64-bit \nJava JDK 1.8_181\n (this is necessary so Jep can install properly).\n\n\nSelect \nDevelopment Tools\n as the installation options\n\n\nMake note of where it installs on your computer (the default is C:\\ProgramFiles\\Java\\jdk1.8.0_181)\n\n\n\n\n\n\n\n\nSet the environment variables:\n\n\n\n\nAccess the Environment Variables window by typing \"env\" in the start bar, hitting enter, and clicking on the \"Environment Variables...\" button at the bottom of the \"System Properties\" window\n\n\nCreate the variables in their respective locations using the \nNew...\n buttons\n\n\nUser Variables: \nPYTHONPATH\n and \nPYTHONHOME\n\n\n\n\nSystem Variable: \nJAVA_HOME\n\n\n\n\n\n\nIf PYTHONHOME is not set, the \ngridslice\n Python module will not be installed or available\n\n\n\n\n\n\n\n\n\n\n\n\nDownload and install 64-bit Microsoft Visual Studio C++ Build Tools\n\n\n\n\nTo access the page linked above you will need a Microsoft account\n\n\nDownload the executable for \nBuild Tools for Visual Studio 2019 (version 16.9)\n\n\nAllow it to run some pre-installations\n\n\nThe installer will pop up as shown below.  Make sure to select the \nC++ build tools\n (upper left), and then view the \nInstallation details\n on the right\n\n\nScroll down and check the \nMSVC v140 - VS 2015 C++ build tools\n\n\n\n\n\n\n\n\nInstall dependent Python packages\n\n\nOnce the installer has finished, close the installer. Another window is present and there is an option to \nlaunch\n a command terminal\n\n\n\nClick that and run the following:\n\n\npip install numpy==1.15.1\n\n\npip install jep==3.8.2\n\n\n\n\n\n\nThese must be run as two separate commands, as stated above for all derived parameters to display properly.\n\n\n\n\n\n\n\n\n\n\nDownload and install: \nawips-cave.msi\n \n\n\nIn addition to the application directory, the MSI installer will attempt to copy the \ngridslice\n shared library to \n$PYTHONHOME/Dlls/\n.  If the \n$PYTHONHOME\n environmental variable is not defined \ngridslice\n will not be installed.  You can check to see if it was installed in the Dlls directory after you have completed steps 1-3.\n\n\n\n\n\n\nCAVE will still run without gridslice, but certain bundles which use derived parameters, such as \nisentropic analysis\n, will not load.\n\n\n\n\n\n\n\n\nRun CAVE\n\uf0c1\n\n\nTo run CAVE, either:\n\n\n\n\nType \"cave\" in the start bar and hit enter\n\n\nFind and run CAVE app in the file browser:  C:\\Program Files\\Unidata\\AWIPS CAVE\\cave.exe\n\n\n\n\n\n\nmacOS \n\uf0c1\n\n\nLatest Version: 18.2.1-3\n\n\nSystem Requirements\n\uf0c1\n\n\n\n\nWill need admin privileges to install \nawips-python.pkg\n\n\n\n\nNVIDIA Graphics card is recommended, however some Intel Graphics cards will support a majority of the functionality\n\n\n\n\nMost AMD graphics cards are not supported\n\n\n\n\n\n\n\n\nDownload and Installation Instructions\n\uf0c1\n\n\n\n\n\n\nDownload and install: \nawips-python.pkg\n \n  \n(This step requires administrative privileges)\n\n\n\n\nOnce downloaded, double click and the installer will launch with the following screens, \nplease keep the default selections\n:\n\n\n\n\n\n\n\n\n\n\n\n\nBetween these steps it will prompt for an administrator's password\n\n\n\n\n\n\n\n\nThe awips-python.pkg is not necessarily required, and CAVE will still run without it, but any derived data such as barbs, arrows, and various grid products will not render without having \njep\n installed (it is assumed to be in /Library/Python/2.7/site-packages/jep/)\n\n\n\n\n\n\n\n\nDownload and install: \nawips-cave.dmg\n \n\n\n\n\n\n\nEither use the default location, which is in the system-wide \"Applications\" directory, by clicking and dragging the CAVE icon into the Applications folder, in the window that pops up when installing:\n\n\n\n\n\n\n\n\nOr open a new Finder window to your [user home]/Applications/ directory (if it doesn't exist, simply create a new folder with the name \"Applications\"), and drag the CAVE icon into that folder:\n\n\n\n\n\nThis will install CAVE as an application and set the local cache to \n~/Library/caveData\n\n\n\n\n\n\n\n\nRun CAVE\n\uf0c1\n\n\nTo run CAVE either:\n\n\n\n\nUse the System Menu Go > Applications > CAVE\n\n\nType \u2318 + Spacebar and then type \"cave\", the application should appear and you can hit \nenter\n to run it\n\n\n\n\n\n\nThe first time CAVE is opened, it will ask you if you are sure you want to run it, because it was downloaded from the internet and not the Apple Store.  This is normal, and hit Open.  Your message my differ slightly but should look like the image below:\n\n\n\n\n\n\nMacOS Monterey Warning\n\uf0c1\n\n\nIf you are running MacOS Monterey, you may see the following message when starting CAVE:\n\n\n\n\nThis message can be ignored, and will hopefully go away when we release version 20+ of AWIPS.\n\n\n\n\nEDEX Connection\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\nLocal Cache\n\uf0c1\n\n\nAfter connecting to an EDEX server, you will have a local directory named \ncaveData\n which contains files synced from EDEX as well as a client-side cache for data and map resources.\n\n\nYou can reset CAVE by removing the \ncaveData\n directory and reconnecting 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\n\n\nLinux: \n/home/<user>/caveData/\n\n\nmacOS: \n/Users/<user>/Library/caveData/\n\n\nWindows: \nC:\\Users\\<user>\\caveData\\\n\n\n\n\n\n\nUninstalling CAVE (Linux)\n\uf0c1\n\n\nThese are instructions to manually uninstall CAVE. However, the \nawips_install.sh\n script will do these steps for you if you are installing a newer version of CAVE.\n\n\n1. Make sure you have exited out of any CAVE sessions\n\n\n2. Remove currently installed CAVE\n\n\nsudo yum clean all\nsudo yum groupremove \"AWIPS CAVE\"\n\n\n\n\n\nIf you are having trouble removing a group, see the \ntroubleshooting\n section.\n\n\n\n\n3. Check to make sure all awips rpms have been removed\n\n\nrpm -qa | grep awips2\n\n\n\nIf you still have rpms installed, remove them\n\n\nsudo yum remove awips2-*\n\n\n\n4. Remove the cave directory in /awips2 and caveData from your home directory\n\n\nrm -rf /awips2/cave\nrm -rf ~/caveData",
+            "text": "Install CAVE\n\uf0c1\n\n\nCAVE is the \nC\nommon \nA\nWIPS \nV\nisualization \nE\nnvironment that is used for rendering and analyzing data for AWIPS.  Unidata supports CAVE to work on three platforms: \nCentos (Redhat) Linux\n, \nWindows\n, and \nmacOS\n.  The installer may require administrator priviledges to install and may require other system changes (environment variables, etc) as well.\n\n\n\n\nLatest CAVE Versions\n\uf0c1\n\n\n\n\nLinux: 18.2.1-4\n\n\nWindows: 18.2.1-3\n\n\nMac: 18.2.1-3\n\n\n\n\nView release notes\n\n\n\n\nGeneral Requirements\n\uf0c1\n\n\nRegardless of what Operating System CAVE is running on, these general requirements are recommended in order for CAVE to perform optimally:\n\n\n\n\n\n\nLocal machine\n\n\n\n\nRunning CAVE via X11 forwarding or ssh tunneling is \nnot\n supported. Using a \nVNC connection is the only remote option\n, and may result in worse performance than running locally.\n\n\n\n\n\n\n\n\nJava 1.8\n\n\n\n\nOpenGL 2.0 Compatible Devices\n\n\nAt least 4GB RAM\n\n\nAt least 2GB Disk Space for Caching\n\n\nNVIDIA Graphics Card\n\n\n\n\nLatest NVIDIA Driver\n\n\n\n\nWhile other graphics cards \nmay\n work, NVIDIA Quadro graphics card is recommended for full visualization capability\n\n\n\n\n\n\n\n\n\n\nLinux \n\uf0c1\n\n\nLatest Version: 18.2.1-4\n\n\nSystem Requirements\n\uf0c1\n\n\n\n\n64 bit CentOS/Red Hat 7\n\n\n\n\nDownload and Installation Instructions\n\uf0c1\n\n\n\n\nDownload the following installer: \nawips_install.sh\n \n\n\nIn a terminal, go to the download directory \n\n\nMake the installer an executable by running: \nchmod 755 awips_install.sh\n\n\nRun the installer: \nsudo ./awips_install.sh --cave\n\n\nThis will install the application in \n/awips2/cave/\n and set the local cache to \n~/caveData/\n\n\n\n\n\n\n\n\nRun CAVE\n\uf0c1\n\n\nTo run CAVE either:\n\n\n\n\nUse the terminal and type the command \ncave\n\n\nFind the application in the Linux Desktop menu: Applications > Internet > AWIPS CAVE\n\n\n\n\n\n\nWindows \n\uf0c1\n\n\nLatest Version: 18.2.1-3\n\n\nFor Windows, Unidata offers two installation options: a \nLinux Virtual Machine\n, or a \nDirect Windows Installation\n.\n\n\nCurrently, the \nvirtual machine (VM)\n is the recommended form of install for those who do not have administrative priviledges on the machine, or beginners who want a simpler installation process.  \n\n\n\n\nAt the moment, the VM option may not render all products in CAVE (ex. RGB composites of satellite imagery)\n\n\n\n\nThe \ndirect installation method\n is recommended for those who have administrative priviledges and a little bit of experience installing more software.\n\n\nMethod 1: Linux Virtual Machine\n\uf0c1\n\n\nThis method is recommended for beginners, or those with less computer knowledge as it is a very simple installation, however at this time, some CAVE functionality may be missing (ex: rendering RGB satellite images).\n\n\nSystem Requirements\n\uf0c1\n\n\n\n\nVMWare Workstation Player\n must be installed (free software)\n\n\n\n\nDownload and Installation Instructions\n\uf0c1\n\n\n\n\nDownload the zipped file containing the virtual machine: \nunidata_cave.zip\n \n\n\nUnzip the folder by right-clicking and selecting \"Extract All\".  All files will be extracted into a new folder.\n\n\nOpen VMWare Player and go to \nPlayer\n > \nFile...\n > \nOpen\n and locate the folder that was created from the downloaded zipped file.  Select the file called \n\"CentOS 7 - Unidata CAVE 18-1-1.vmx\"\n.\n\n\nRun this new VM option.  If it asks if it's been moved or copied, select \n\"I Copied It\"\n.\n\n\nThere will be a user in the Linux machine named \"awips\" and the password is \"awips\"\n\n\nThe root password is \"unidataAWIPS\" if ever needed\n\n\n\n\n\n\n\n\nRun CAVE\n\uf0c1\n\n\nOnce inside the VM, to run CAVE either:\n\n\n\n\nUse the desktop icon \n\n\nUse the terminal and type the command \ncave\n\n\nFind the application in the Linux Desktop menu: Applications > Internet > AWIPS CAVE\n\n\n\n\nMethod 2: Direct Windows Install\n\uf0c1\n\n\nThis method is recommended for personal use and requires Administrative priviledges.  It should enable full CAVE capability, but it is a bit lengthy and might take about 20 minutes or so to complete.\n\nFor additional assistance we have created an \ninstallation video\n that walks through the steps below.\n\n\n\n\nIt is important to use the exact versions of software that we link to or specify in our instructions.  Deviations may cause installation problems or failures.\n\n\n\n\nSystem Requirements\n\uf0c1\n\n\n\n\n64-bit Miniconda3 (Python3.7 - 4.8.2)\n\n\nPython3 (comes with Miniconda installation)\n\n\n64-bit Java JDK 1.8 (1.8_181)\n\n\n64-bit Visual C++ Build Tools 2015 and 2019\n\n\nNumpy (1.15.1)\n\n\nJep (3.8.2)\n\n\nUser Variable PATH must have miniconda3 location\n\n\nUser Variables PYTHONHOME and PYTHONPATH must be defined\n\n\nSystem Variable JAVA_HOME must be defined\n\n\n\n\nDownload and Installation Instructions\n\uf0c1\n\n\n\n\nDownload and install 64-bit \nMiniconda Python3.7 version 4.8.2 for Windows\n\n\nAllow\n Miniconda3 to set \nPATH\n and other environment variables\n\n\nRegister\n miniconda as the default python\n\n\n\n\n\n\n\nDownload and install the 64-bit \nJava JDK 1.8_181\n (this is necessary so Jep can install properly).\n\n\nSelect \nDevelopment Tools\n as the installation options\n\n\nMake note of where it installs on your computer (the default is C:\\ProgramFiles\\Java\\jdk1.8.0_181)\n\n\n\n\n\n\n\n\nSet the environment variables:\n\n\n\n\nAccess the Environment Variables window by typing \"env\" in the start bar, hitting enter, and clicking on the \"Environment Variables...\" button at the bottom of the \"System Properties\" window\n\n\nCreate the variables in their respective locations using the \nNew...\n buttons\n\n\nUser Variables: \nPYTHONPATH\n and \nPYTHONHOME\n\n\n\n\nSystem Variable: \nJAVA_HOME\n\n\n\n\n\n\nIf PYTHONHOME is not set, the \ngridslice\n Python module will not be installed or available\n\n\n\n\n\n\n\n\n\n\n\n\nDownload and install 64-bit Microsoft Visual Studio C++ Build Tools\n\n\n\n\nTo access the page linked above you will need a Microsoft account\n\n\nDownload the executable for \nBuild Tools for Visual Studio 2019 (version 16.9)\n\n\nAllow it to run some pre-installations\n\n\nThe installer will pop up as shown below.  Make sure to select the \nC++ build tools\n (upper left), and then view the \nInstallation details\n on the right\n\n\nScroll down and check the \nMSVC v140 - VS 2015 C++ build tools\n\n\n\n\n\n\n\n\nInstall dependent Python packages\n\n\nOnce the installer has finished, close the installer. Another window is present and there is an option to \nlaunch\n a command terminal\n\n\n\nClick that and run the following:\n\n\npip install numpy==1.15.1\n\n\npip install jep==3.8.2\n\n\n\n\n\n\nThese must be run as two separate commands, as stated above for all derived parameters to display properly.\n\n\n\n\n\n\n\n\n\n\nDownload and install: \nawips-cave.msi\n \n\n\nIn addition to the application directory, the MSI installer will attempt to copy the \ngridslice\n shared library to \n$PYTHONHOME/Dlls/\n.  If the \n$PYTHONHOME\n environmental variable is not defined \ngridslice\n will not be installed.  You can check to see if it was installed in the Dlls directory after you have completed steps 1-3.\n\n\n\n\n\n\nCAVE will still run without gridslice, but certain bundles which use derived parameters, such as \nisentropic analysis\n, will not load.\n\n\n\n\n\n\n\n\nRun CAVE\n\uf0c1\n\n\nTo run CAVE, either:\n\n\n\n\nType \"cave\" in the start bar and hit enter\n\n\nFind and run CAVE app in the file browser:  C:\\Program Files\\Unidata\\AWIPS CAVE\\cave.exe\n\n\n\n\n\n\nmacOS \n\uf0c1\n\n\nLatest Version: 18.2.1-3\n\n\nSystem Requirements\n\uf0c1\n\n\n\n\nWill need admin privileges to install \nawips-python.pkg\n\n\n\n\nNVIDIA Graphics card is recommended, however some Intel Graphics cards will support a majority of the functionality\n\n\n\n\nMost AMD graphics cards are not supported\n\n\n\n\n\n\n\n\nDownload and Installation Instructions\n\uf0c1\n\n\n\n\n\n\nDownload and install: \nawips-python.pkg\n \n  \n(This step requires administrative privileges)\n\n\n\n\nOnce downloaded, double click and the installer will launch with the following screens, \nplease keep the default selections\n:\n\n\n\n\n\n\n\n\n\n\n\n\nBetween these steps it will prompt for an administrator's password\n\n\n\n\n\n\n\n\nThe awips-python.pkg is not necessarily required, and CAVE will still run without it, but any derived data such as barbs, arrows, and various grid products will not render without having \njep\n installed (it is assumed to be in /Library/Python/2.7/site-packages/jep/)\n\n\n\n\n\n\n\n\nDownload and install: \nawips-cave.dmg\n \n\n\n\n\n\n\nEither use the default location, which is in the system-wide \"Applications\" directory, by clicking and dragging the CAVE icon into the Applications folder, in the window that pops up when installing:\n\n\n\n\n\n\n\n\nOr open a new Finder window to your [user home]/Applications/ directory (if it doesn't exist, simply create a new folder with the name \"Applications\"), and drag the CAVE icon into that folder:\n\n\n\n\n\nThis will install CAVE as an application and set the local cache to \n~/Library/caveData\n\n\n\n\n\n\n\n\nRun CAVE\n\uf0c1\n\n\nTo run CAVE either:\n\n\n\n\nUse the System Menu Go > Applications > CAVE\n\n\nType \u2318 + Spacebar and then type \"cave\", the application should appear and you can hit \nenter\n to run it\n\n\n\n\n\n\nThe first time CAVE is opened, it will ask you if you are sure you want to run it, because it was downloaded from the internet and not the Apple Store.  This is normal, and hit Open.  Your message my differ slightly but should look like the image below:\n\n\n\n\n\n\nMacOS Monterey Warning\n\uf0c1\n\n\nIf you are running MacOS Monterey, you may see the following message when starting CAVE:\n\n\n\n\nThis message can be ignored, and will hopefully go away when we release version 20+ of AWIPS.\n\n\n\n\nEDEX Connection\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\nLocal Cache\n\uf0c1\n\n\nAfter connecting to an EDEX server, you will have a local directory named \ncaveData\n which contains files synced from EDEX as well as a client-side cache for data and map resources.\n\n\nYou can reset CAVE by removing the \ncaveData\n directory and reconnecting 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\n\n\nLinux: \n/home/<user>/caveData/\n\n\nmacOS: \n/Users/<user>/Library/caveData/\n\n\nWindows: \nC:\\Users\\<user>\\caveData\\\n\n\n\n\n\n\nUninstalling CAVE (Linux)\n\uf0c1\n\n\nThese are instructions to manually uninstall CAVE. However, the \nawips_install.sh\n script will do these steps for you if you are installing a newer version of CAVE.\n\n\n1. Make sure you have exited out of any CAVE sessions\n\n\n2. Remove currently installed CAVE\n\n\nsudo yum clean all\nsudo yum groupremove \"AWIPS CAVE\"\n\n\n\n\n\nIf you are having trouble removing a group, see the \ntroubleshooting\n section.\n\n\n\n\n3. Check to make sure all awips rpms have been removed\n\n\nrpm -qa | grep awips2\n\n\n\nIf you still have rpms installed, remove them\n\n\nsudo yum remove awips2-*\n\n\n\n4. Remove the cave directory in /awips2 and caveData from your home directory\n\n\nrm -rf /awips2/cave\nrm -rf ~/caveData",
             "title": "Install CAVE"
         },
         {
@@ -97,7 +97,7 @@
         },
         {
             "location": "/install/install-cave/#latest-cave-versions",
-            "text": "Linux: 18.2.1-3  Windows: 18.2.1-3  Mac: 18.2.1-3   View release notes",
+            "text": "Linux: 18.2.1-4  Windows: 18.2.1-3  Mac: 18.2.1-3   View release notes",
             "title": "Latest CAVE Versions"
         },
         {
@@ -107,7 +107,7 @@
         },
         {
             "location": "/install/install-cave/#linux",
-            "text": "Latest Version: 18.2.1-3",
+            "text": "Latest Version: 18.2.1-4",
             "title": "Linux "
         },
         {
@@ -212,7 +212,7 @@
         },
         {
             "location": "/install/install-edex/",
-            "text": "Install EDEX \n\uf0c1\n\n\nEDEX is the \nE\nnvironmental \nD\nata \nEx\nchange system that represents the backend server for AWIPS.  EDEX is only supported for Linux systems: CentOS and RHEL, and ideally, it should be on its own dedicated machine.  It requires administrator priviledges to make root-level changes. EDEX can run on a single machine or be spread across multiple machines.  To learn more about that please look at \nDistributed EDEX, Installing Across Multiple Machines\n\n\n\n\nLatest Version\n\uf0c1\n\n\n18.2.1-3\n\n\nView release notes\n\n\n\n\nSystem requirements\n\uf0c1\n\n\n\n\n64-bit CentOS/RHEL 7\n\n\n16+ CPU cores (each CPU core can run a decorder in parallel)\n\n\n24GB RAM\n\n\n700GB+ Disk Space\n\n\ngcc-c++ package\n\n\nRun \nrpm -qa | grep gcc-c++\n to verify if the package is installed\n\n\nIf it is not installed, run \nyum install gcc-c++\n to install the package\n\n\n\n\n\n\nA \nSolid State Drive (SSD)\n is recommended\n\n\nA SSD should be mounted either to \n/awips2\n (to contain the entire EDEX system) or to \n/awips2/edex/data/hdf5\n (to contain the large files in the decoded data store). EDEX can scale to any system by adjusting the incoming LDM data feeds or adjusting the resources (CPU threads) allocated to each data type.\n\n\n\n\n\n\n\n\n\n\nEDEX is only supported for 64-bit CentOS and RHEL 7 Operating Systems.\n\n\n\n\n\n\nEDEX is \nnot\n supported in Debian, Ubuntu, SUSE, Solaris, macOS, or Windows. You may have luck with Fedora Core 12 to 14 and Scientific Linux, but we will not provide support.\n\n\n\n\n\n\nDownload and Installation Instructions\n\uf0c1\n\n\nThe first 3 steps should all be run as \nroot\n\n\n1. Install EDEX\n\uf0c1\n\n\nDownload and run the installer: \nawips_install.sh\n \n\n\nwget https://downloads.unidata.ucar.edu/awips2/current/linux/awips_install.sh\nchmod 755 awips_install.sh\nsudo ./awips_install.sh --edex\n\n\n\n\n\nawips_install.sh --edex\n will perform the following steps (it's always a good idea to review downloaded shell scripts):\n\n\n\n\nChecks to see if EDEX is currently running, if so stops the processes with the \nedex stop\n command\n\n\nIf EDEX is installed, asks the user if it can be removed and where to backup the data to and does a \nyum groupremove awips2-server\n\n\nIf the user/group awips:fxalpha does not exist, it gets created\n\n\nSaves the appropriate yum repo file to \n/etc/yum.repos.d/awips2.repo\n\n\nIncreases process and file limits for the the \nawips\n account in \n/etc/security/limits.conf\n\n\nCreates \n/awips2/data_store\n if it does not exist already\n\n\nRuns \nyum groupinstall awips2-server\n\n\n\n\n\n\n\n\nIf you receive an error relating to yum, then please run\n\n\nsudo su - -c \"[PATH_TO_INSTALL_FILE]/awips_install.sh --edex\"\n\n\n\n\n2. EDEX Setup\n\uf0c1\n\n\nThe external and localhost addresses need to be specified in \n/etc/hosts\n\n\n127.0.0.1         localhost    localhost.localdomain\nXXX.XXX.XXX.XXX   edex-cloud   edex-cloud.unidata.ucar.edu\n\n\n\n\n3. Configure iptables\n\uf0c1\n\n\nThis should be a one time configuration change. Configure iptables to allow TCP connections on ports 9581 and 9582 if you want to serve data publicly to CAVE clients and the Python API.\n\n\nOpen Port 9588\n\uf0c1\n\n\nIf you are running a Registry (Data Delivery) server, you will also want to open port \n9588\n.\n\n\nTo open ports to all connections\n\uf0c1\n\n\nvi /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 9581 -j ACCEPT\n-A INPUT -m state --state NEW -m tcp -p tcp --dport 9582 -j ACCEPT\n#-A INPUT -m state --state NEW -m tcp -p tcp --dport 9588 -j ACCEPT # for registry/dd\n-A INPUT -j REJECT --reject-with icmp-host-prohibited\n-A FORWARD -j REJECT --reject-with icmp-host-prohibited\nCOMMIT\n\n\n\nTo open ports to specific IP addresses\n\uf0c1\n\n\nIn this example, the IP range \n128.117.140.0/24\n will match all 128.117.140.* addresses, while \n128.117.156.0/24\n will match 128.117.156.*.\n\n\nvi /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 9581 -j ACCEPT\n-A EDEX -m state --state NEW -p tcp --dport 9582 -j ACCEPT\n#-A EDEX -m state --state NEW -p tcp --dport 9588 -j ACCEPT # for registry/dd\n-A EDEX -j REJECT\nCOMMIT\n\n\n\nRestart iptables\n\uf0c1\n\n\nservice iptables restart\n\n\n\nTroubleshooting\n\uf0c1\n\n\nFor CentOS 7 error:\n\n\nRedirecting to /bin/systemctl restart  iptables.service \nFailed to restart iptables.service: Unit iptables.service failed to load: No such file or directory.\n\n\n\nThe solution is:\n\n\nyum install iptables-services\nsystemctl enable iptables\nservice iptables restart\n\n\n\n4. Start EDEX\n\uf0c1\n\n\n\n\nThese steps should be run as user \nawips\n with sudo.  Switch to the user by running \nsu - awips\n.\n\n\n\n\nedex start\n\n\n\nTo manually start, stop, and restart:\n\n\nservice edex_postgres start\nservice httpd-pypies start\nservice qpidd start\nservice edex_camel start\n\n\n\nThe fifth service, \nedex_ldm\n, does \nnot run at boot\n to prevent filling up disk space if EDEX is not running. Start ldm manually:\n\n\nservice edex_ldm start\n\n\n\nTo restart EDEX\n\n\nedex restart\n\n\n\n\n\nAdditional Notes\n\uf0c1\n\n\nEnsure SELinux is Disabled\n\uf0c1\n\n\nvi /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\n\n\n\n\n\nRead more about selinux at \nredhat.com\n\n\n\n\n\n\nSSD Mount\n\uf0c1\n\n\nThough a Solid State Drive is not required, it is \nstrongly encouraged\n in order to handle the amount of disk IO for real-time IDD feeds.\n\n\nThe simplest configuration would be to mount an 500GB+ SSD to \n/awips2\n to contain both the installed software (approx. 20GB) and the real-time data (approx. 150GB per day).\n\n\nThe default \npurge rules\n are configured such that the processed data in \n/awips2\n does not exceed 450GB. The raw data is located in \n/awips2/data_store\n, and is scoured every hour and should not exceed 50GB.\n\n\nIf you want to increase EDEX data retention you should mount a large disk to \n/awips2/edex/data/hdf5\n since this will be where the archived processed data exists, and any case studies created.\n\n\nFilesystem      Size  Used Avail Use% Mounted on\n/dev/sda1        30G  2.5G   26G   9% /\ntmpfs            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\n\n\n\n\n\nConfigure LDM Feeds\n\uf0c1\n\n\nEDEX installs its own version of the LDM to the directory \n/awips2/ldm\n.  As with a the default LDM configuration, two files are used to control what IDD feeds are ingested:\n\n\nConfiguration file: /awips2/ldm/etc/ldmd.conf\n\uf0c1\n\n\nThis file specifies an upstream LDM server to request data from, and what feeds to request:\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\n\n\n\n\n\nRead more about ldmd.conf in the LDM User Manual\n\n\n\n\nConfiguration File: /awips2/ldm/etc/pqact.conf\n\uf0c1\n\n\nThis file specifies the WMO headers and file pattern actions to request:\n\n\n# 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\n\n\n\n\n\nRead more about pqact.conf in the LDM User Manual\n\n\n\n\n\n\nSee available AWIPS LDM feeds\n\n\n\n\nConfiguration File: /awips2/ldm/etc/registry.xml\n\uf0c1\n\n\nThis file specifies configuration and runtime parameters. If you are pulling in a lot of data, you may want to consider increasing your LDM queue size:\n\n\n  <queue>\n    <path>/awips2/ldm/var/queues/ldm.pq</path>\n    <size>24GB</size>\n    <slots>default</slots>\n  </queue>\n\n\n\n\n\nRead more about registry.xml in the LDM User Manual\n\n\n\n\n\n\nDirectories to Know\n\uf0c1\n\n\n\n\n/awips2\n - Contains all of the installed AWIPS software.\n\n\n/awips2/edex/logs\n - EDEX logs.\n\n\n/awips2/httpd_pypies/var/log/httpd\n - httpd-pypies logs.\n\n\n/awips2/database/data/pg_log\n - PostgreSQL logs.\n\n\n/awips2/qpid/log\n - Qpid logs.\n\n\n/awips2/edex/data/hdf5\n - HDF5 data store.\n\n\n/awips2/edex/data/utility\n - Localization store and configuration files.\n\n\n/awips2/ldm/etc\n - Location of \nldmd.conf\n and \npqact.conf\n\n\n/awips2/ldm/logs\n - LDM logs.\n\n\n/awips2/data_store\n - Raw data store.\n\n\n/awips2/data_store/ingest\n - Manual data ingest endpoint.\n\n\n\n\n\n\nWhat Version is my EDEX?\n\uf0c1\n\n\nrpm -qa | grep awips2-edex\n\n\n\n\n\nUninstalling EDEX\n\uf0c1\n\n\nThese are instructions to manually uninstall EDEX. However, the \nawips_install.sh\n script will do all of these steps for you if you are installing a newer version of EDEX.\n\n\n1. Make sure all EDEX processes are stopped\n\n\nsudo edex stop\nsudo edex status\n\n[edex status]\n postgres    :: not running\n pypies      :: not running\n qpid        :: not running\n EDEXingest  :: not running\n EDEXgrib    :: not running\n EDEXrequest :: not running\n ldmadmin    :: not running\n\n\n\n2. Backup any important configuration files that you may want to reference\n\n\nHere are some possible important directories/files to backup:\n\n\n/awips2/database/data/pg_hba.conf\n/awips2/edex/data/utility/*\n/awips2/edex/bin/*\n/awips2/ldm/*\n/awips2/dev/*\n/awips2/edex/conf*\n/awips2/edex/etc/*\n/awips2/edex/logs/*\n/usr/bin/edex/*\n/etc/init.d/edexServiceList\n\n\n\n3. See what AWIPS yum groups are currently installed\n\n\nIn this case the \nAWIPS EDEX Server\n group is installed\n\n\nsudo yum grouplist\n\nAvailable Environment Groups:\n   Minimal Install\n   Compute Node\n   Infrastructure Server\n   File and Print Server\n   Cinnamon Desktop\n   MATE Desktop\n   Basic Web Server\n   Virtualization Host\n   Server with GUI\n   GNOME Desktop\n   KDE Plasma Workspaces\n   Development and Creative Workstation\nInstalled Groups:\n   AWIPS EDEX Server\n   Development Tools\nAvailable Groups:\n   AWIPS ADE SERVER\n   AWIPS CAVE\n   AWIPS Development\n   AWIPS EDEX DAT Server\n   AWIPS EDEX Database/Request Server\n   AWIPS EDEX Decode/Ingest Node (No Database, PyPIES, GFE)\n   Cinnamon\n   Compatibility Libraries\n   Console Internet Tools\n   Educational Software\n   Electronic Lab\n   Fedora Packager\n   General Purpose Desktop\n   Graphical Administration Tools\n   Haskell\n   LXQt Desktop\n   Legacy UNIX Compatibility\n   MATE\n   Milkymist\n   Scientific Support\n   Security Tools\n   Smart Card Support\n   System Administration Tools\n   System Management\n   TurboGears application framework\n   Xfce\n\n\n\n4. Remove any currently installed AWIPS yum groups\n\n\nsudo yum clean all\nsudo yum groupremove \"AWIPS EDEX Server\"\n\n\n\n\n\nIf you are having trouble removing a group, see the \ntroubleshooting\n section.\n\n\n\n\n5. Check to make sure all awips rpms have been removed\n\n\nrpm -qa | grep awips2\n\n\n\nIf you still have rpms installed, remove them\n\n\nsudo yum remove awips2-*\n\n\n\n6. Remove everything in the /awips2 directory\n\n\nrm -rf /awips2/*",
+            "text": "Install EDEX \n\uf0c1\n\n\nEDEX is the \nE\nnvironmental \nD\nata \nEx\nchange system that represents the backend server for AWIPS.  EDEX is only supported for Linux systems: CentOS and RHEL, and ideally, it should be on its own dedicated machine.  It requires administrator priviledges to make root-level changes. EDEX can run on a single machine or be spread across multiple machines.  To learn more about that please look at \nDistributed EDEX, Installing Across Multiple Machines\n\n\n\n\nLatest Version\n\uf0c1\n\n\n18.2.1-4\n\n\nView release notes\n\n\n\n\nSystem requirements\n\uf0c1\n\n\n\n\n64-bit CentOS/RHEL 7\n\n\n16+ CPU cores (each CPU core can run a decorder in parallel)\n\n\n24GB RAM\n\n\n700GB+ Disk Space\n\n\ngcc-c++ package\n\n\nRun \nrpm -qa | grep gcc-c++\n to verify if the package is installed\n\n\nIf it is not installed, run \nyum install gcc-c++\n to install the package\n\n\n\n\n\n\nA \nSolid State Drive (SSD)\n is recommended\n\n\nA SSD should be mounted either to \n/awips2\n (to contain the entire EDEX system) or to \n/awips2/edex/data/hdf5\n (to contain the large files in the decoded data store). EDEX can scale to any system by adjusting the incoming LDM data feeds or adjusting the resources (CPU threads) allocated to each data type.\n\n\n\n\n\n\n\n\n\n\nEDEX is only supported for 64-bit CentOS and RHEL 7 Operating Systems.\n\n\n\n\n\n\nEDEX is \nnot\n supported in Debian, Ubuntu, SUSE, Solaris, macOS, or Windows. You may have luck with Fedora Core 12 to 14 and Scientific Linux, but we will not provide support.\n\n\n\n\n\n\nDownload and Installation Instructions\n\uf0c1\n\n\nThe first 3 steps should all be run as \nroot\n\n\n1. Install EDEX\n\uf0c1\n\n\nDownload and run the installer: \nawips_install.sh\n \n\n\nwget https://downloads.unidata.ucar.edu/awips2/current/linux/awips_install.sh\nchmod 755 awips_install.sh\nsudo ./awips_install.sh --edex\n\n\n\n\n\nawips_install.sh --edex\n will perform the following steps (it's always a good idea to review downloaded shell scripts):\n\n\n\n\nChecks to see if EDEX is currently running, if so stops the processes with the \nedex stop\n command\n\n\nIf EDEX is installed, asks the user if it can be removed and where to backup the data to and does a \nyum groupremove awips2-server\n\n\nIf the user/group awips:fxalpha does not exist, it gets created\n\n\nSaves the appropriate yum repo file to \n/etc/yum.repos.d/awips2.repo\n\n\nIncreases process and file limits for the the \nawips\n account in \n/etc/security/limits.conf\n\n\nCreates \n/awips2/data_store\n if it does not exist already\n\n\nRuns \nyum groupinstall awips2-server\n\n\n\n\n\n\n\n\nIf you receive an error relating to yum, then please run\n\n\nsudo su - -c \"[PATH_TO_INSTALL_FILE]/awips_install.sh --edex\"\n\n\n\n\n2. EDEX Setup\n\uf0c1\n\n\nThe external and localhost addresses need to be specified in \n/etc/hosts\n\n\n127.0.0.1         localhost    localhost.localdomain\nXXX.XXX.XXX.XXX   edex-cloud   edex-cloud.unidata.ucar.edu\n\n\n\n\n3. Configure iptables\n\uf0c1\n\n\nThis should be a one time configuration change. Configure iptables to allow TCP connections on ports 9581 and 9582 if you want to serve data publicly to CAVE clients and the Python API.\n\n\nOpen Port 9588\n\uf0c1\n\n\nIf you are running a Registry (Data Delivery) server, you will also want to open port \n9588\n.\n\n\nTo open ports to all connections\n\uf0c1\n\n\nvi /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 9581 -j ACCEPT\n-A INPUT -m state --state NEW -m tcp -p tcp --dport 9582 -j ACCEPT\n#-A INPUT -m state --state NEW -m tcp -p tcp --dport 9588 -j ACCEPT # for registry/dd\n-A INPUT -j REJECT --reject-with icmp-host-prohibited\n-A FORWARD -j REJECT --reject-with icmp-host-prohibited\nCOMMIT\n\n\n\nTo open ports to specific IP addresses\n\uf0c1\n\n\nIn this example, the IP range \n128.117.140.0/24\n will match all 128.117.140.* addresses, while \n128.117.156.0/24\n will match 128.117.156.*.\n\n\nvi /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 9581 -j ACCEPT\n-A EDEX -m state --state NEW -p tcp --dport 9582 -j ACCEPT\n#-A EDEX -m state --state NEW -p tcp --dport 9588 -j ACCEPT # for registry/dd\n-A EDEX -j REJECT\nCOMMIT\n\n\n\nRestart iptables\n\uf0c1\n\n\nservice iptables restart\n\n\n\nTroubleshooting\n\uf0c1\n\n\nFor CentOS 7 error:\n\n\nRedirecting to /bin/systemctl restart  iptables.service \nFailed to restart iptables.service: Unit iptables.service failed to load: No such file or directory.\n\n\n\nThe solution is:\n\n\nyum install iptables-services\nsystemctl enable iptables\nservice iptables restart\n\n\n\n4. Start EDEX\n\uf0c1\n\n\n\n\nThese steps should be run as user \nawips\n with sudo.  Switch to the user by running \nsu - awips\n.\n\n\n\n\nedex start\n\n\n\nTo manually start, stop, and restart:\n\n\nservice edex_postgres start\nservice httpd-pypies start\nservice qpidd start\nservice edex_camel start\n\n\n\nThe fifth service, \nedex_ldm\n, does \nnot run at boot\n to prevent filling up disk space if EDEX is not running. Start ldm manually:\n\n\nservice edex_ldm start\n\n\n\nTo restart EDEX\n\n\nedex restart\n\n\n\n\n\nAdditional Notes\n\uf0c1\n\n\nEnsure SELinux is Disabled\n\uf0c1\n\n\nvi /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\n\n\n\n\n\nRead more about selinux at \nredhat.com\n\n\n\n\n\n\nSSD Mount\n\uf0c1\n\n\nThough a Solid State Drive is not required, it is \nstrongly encouraged\n in order to handle the amount of disk IO for real-time IDD feeds.\n\n\nThe simplest configuration would be to mount an 500GB+ SSD to \n/awips2\n to contain both the installed software (approx. 20GB) and the real-time data (approx. 150GB per day).\n\n\nThe default \npurge rules\n are configured such that the processed data in \n/awips2\n does not exceed 450GB. The raw data is located in \n/awips2/data_store\n, and is scoured every hour and should not exceed 50GB.\n\n\nIf you want to increase EDEX data retention you should mount a large disk to \n/awips2/edex/data/hdf5\n since this will be where the archived processed data exists, and any case studies created.\n\n\nFilesystem      Size  Used Avail Use% Mounted on\n/dev/sda1        30G  2.5G   26G   9% /\ntmpfs            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\n\n\n\n\n\nConfigure LDM Feeds\n\uf0c1\n\n\nEDEX installs its own version of the LDM to the directory \n/awips2/ldm\n.  As with a the default LDM configuration, two files are used to control what IDD feeds are ingested:\n\n\nConfiguration file: /awips2/ldm/etc/ldmd.conf\n\uf0c1\n\n\nThis file specifies an upstream LDM server to request data from, and what feeds to request:\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\n\n\n\n\n\nRead more about ldmd.conf in the LDM User Manual\n\n\n\n\nConfiguration File: /awips2/ldm/etc/pqact.conf\n\uf0c1\n\n\nThis file specifies the WMO headers and file pattern actions to request:\n\n\n# 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\n\n\n\n\n\nRead more about pqact.conf in the LDM User Manual\n\n\n\n\n\n\nSee available AWIPS LDM feeds\n\n\n\n\nConfiguration File: /awips2/ldm/etc/registry.xml\n\uf0c1\n\n\nThis file specifies configuration and runtime parameters. If you are pulling in a lot of data, you may want to consider increasing your LDM queue size:\n\n\n  <queue>\n    <path>/awips2/ldm/var/queues/ldm.pq</path>\n    <size>24GB</size>\n    <slots>default</slots>\n  </queue>\n\n\n\n\n\nRead more about registry.xml in the LDM User Manual\n\n\n\n\n\n\nDirectories to Know\n\uf0c1\n\n\n\n\n/awips2\n - Contains all of the installed AWIPS software.\n\n\n/awips2/edex/logs\n - EDEX logs.\n\n\n/awips2/httpd_pypies/var/log/httpd\n - httpd-pypies logs.\n\n\n/awips2/database/data/pg_log\n - PostgreSQL logs.\n\n\n/awips2/qpid/log\n - Qpid logs.\n\n\n/awips2/edex/data/hdf5\n - HDF5 data store.\n\n\n/awips2/edex/data/utility\n - Localization store and configuration files.\n\n\n/awips2/ldm/etc\n - Location of \nldmd.conf\n and \npqact.conf\n\n\n/awips2/ldm/logs\n - LDM logs.\n\n\n/awips2/data_store\n - Raw data store.\n\n\n/awips2/data_store/ingest\n - Manual data ingest endpoint.\n\n\n\n\n\n\nWhat Version is my EDEX?\n\uf0c1\n\n\nrpm -qa | grep awips2-edex\n\n\n\n\n\nUninstalling EDEX\n\uf0c1\n\n\nThese are instructions to manually uninstall EDEX. However, the \nawips_install.sh\n script will do all of these steps for you if you are installing a newer version of EDEX.\n\n\n1. Make sure all EDEX processes are stopped\n\n\nsudo edex stop\nsudo edex status\n\n[edex status]\n postgres    :: not running\n pypies      :: not running\n qpid        :: not running\n EDEXingest  :: not running\n EDEXgrib    :: not running\n EDEXrequest :: not running\n ldmadmin    :: not running\n\n\n\n2. Backup any important configuration files that you may want to reference\n\n\nHere are some possible important directories/files to backup:\n\n\n/awips2/database/data/pg_hba.conf\n/awips2/edex/data/utility/*\n/awips2/edex/bin/*\n/awips2/ldm/*\n/awips2/dev/*\n/awips2/edex/conf*\n/awips2/edex/etc/*\n/awips2/edex/logs/*\n/usr/bin/edex/*\n/etc/init.d/edexServiceList\n\n\n\n3. See what AWIPS yum groups are currently installed\n\n\nIn this case the \nAWIPS EDEX Server\n group is installed\n\n\nsudo yum grouplist\n\nAvailable Environment Groups:\n   Minimal Install\n   Compute Node\n   Infrastructure Server\n   File and Print Server\n   Cinnamon Desktop\n   MATE Desktop\n   Basic Web Server\n   Virtualization Host\n   Server with GUI\n   GNOME Desktop\n   KDE Plasma Workspaces\n   Development and Creative Workstation\nInstalled Groups:\n   AWIPS EDEX Server\n   Development Tools\nAvailable Groups:\n   AWIPS ADE SERVER\n   AWIPS CAVE\n   AWIPS Development\n   AWIPS EDEX DAT Server\n   AWIPS EDEX Database/Request Server\n   AWIPS EDEX Decode/Ingest Node (No Database, PyPIES, GFE)\n   Cinnamon\n   Compatibility Libraries\n   Console Internet Tools\n   Educational Software\n   Electronic Lab\n   Fedora Packager\n   General Purpose Desktop\n   Graphical Administration Tools\n   Haskell\n   LXQt Desktop\n   Legacy UNIX Compatibility\n   MATE\n   Milkymist\n   Scientific Support\n   Security Tools\n   Smart Card Support\n   System Administration Tools\n   System Management\n   TurboGears application framework\n   Xfce\n\n\n\n4. Remove any currently installed AWIPS yum groups\n\n\nsudo yum clean all\nsudo yum groupremove \"AWIPS EDEX Server\"\n\n\n\n\n\nIf you are having trouble removing a group, see the \ntroubleshooting\n section.\n\n\n\n\n5. Check to make sure all awips rpms have been removed\n\n\nrpm -qa | grep awips2\n\n\n\nIf you still have rpms installed, remove them\n\n\nsudo yum remove awips2-*\n\n\n\n6. Remove everything in the /awips2 directory\n\n\nrm -rf /awips2/*",
             "title": "Install EDEX"
         },
         {
@@ -222,7 +222,7 @@
         },
         {
             "location": "/install/install-edex/#latest-version",
-            "text": "18.2.1-3  View release notes",
+            "text": "18.2.1-4  View release notes",
             "title": "Latest Version"
         },
         {
diff --git a/sitemap.xml b/sitemap.xml
index 74adf14db0..b6815dad64 100644
--- a/sitemap.xml
+++ b/sitemap.xml
@@ -2,197 +2,197 @@
 <urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
     <url>
      <loc>http://unidata.github.io/awips2/</loc>
-     <lastmod>2022-01-05</lastmod>
+     <lastmod>2022-01-11</lastmod>
      <changefreq>daily</changefreq>
     </url>
     <url>
      <loc>http://unidata.github.io/awips2/install/install-cave/</loc>
-     <lastmod>2022-01-05</lastmod>
+     <lastmod>2022-01-11</lastmod>
      <changefreq>daily</changefreq>
     </url>
     <url>
      <loc>http://unidata.github.io/awips2/install/install-edex/</loc>
-     <lastmod>2022-01-05</lastmod>
+     <lastmod>2022-01-11</lastmod>
      <changefreq>daily</changefreq>
     </url>
     <url>
      <loc>http://unidata.github.io/awips2/install/common-problems/</loc>
-     <lastmod>2022-01-05</lastmod>
+     <lastmod>2022-01-11</lastmod>
      <changefreq>daily</changefreq>
     </url>
     <url>
      <loc>http://unidata.github.io/awips2/cave/d2d-perspective/</loc>
-     <lastmod>2022-01-05</lastmod>
+     <lastmod>2022-01-11</lastmod>
      <changefreq>daily</changefreq>
     </url>
     <url>
      <loc>http://unidata.github.io/awips2/cave/maps-views-projections/</loc>
-     <lastmod>2022-01-05</lastmod>
+     <lastmod>2022-01-11</lastmod>
      <changefreq>daily</changefreq>
     </url>
     <url>
      <loc>http://unidata.github.io/awips2/cave/bundles-and-procedures/</loc>
-     <lastmod>2022-01-05</lastmod>
+     <lastmod>2022-01-11</lastmod>
      <changefreq>daily</changefreq>
     </url>
     <url>
      <loc>http://unidata.github.io/awips2/cave/localization-perspective/</loc>
-     <lastmod>2022-01-05</lastmod>
+     <lastmod>2022-01-11</lastmod>
      <changefreq>daily</changefreq>
     </url>
     <url>
      <loc>http://unidata.github.io/awips2/cave/nsharp/</loc>
-     <lastmod>2022-01-05</lastmod>
+     <lastmod>2022-01-11</lastmod>
      <changefreq>daily</changefreq>
     </url>
     <url>
      <loc>http://unidata.github.io/awips2/cave/warngen/</loc>
-     <lastmod>2022-01-05</lastmod>
+     <lastmod>2022-01-11</lastmod>
      <changefreq>daily</changefreq>
     </url>
     <url>
      <loc>http://unidata.github.io/awips2/cave/goes-16-17-satellite/</loc>
-     <lastmod>2022-01-05</lastmod>
+     <lastmod>2022-01-11</lastmod>
      <changefreq>daily</changefreq>
     </url>
     <url>
      <loc>http://unidata.github.io/awips2/cave/d2d-gis-shapefiles/</loc>
-     <lastmod>2022-01-05</lastmod>
+     <lastmod>2022-01-11</lastmod>
      <changefreq>daily</changefreq>
     </url>
     <url>
      <loc>http://unidata.github.io/awips2/cave/d2d-gridded-models/</loc>
-     <lastmod>2022-01-05</lastmod>
+     <lastmod>2022-01-11</lastmod>
      <changefreq>daily</changefreq>
     </url>
     <url>
      <loc>http://unidata.github.io/awips2/cave/d2d-tools/</loc>
-     <lastmod>2022-01-05</lastmod>
+     <lastmod>2022-01-11</lastmod>
      <changefreq>daily</changefreq>
     </url>
     <url>
      <loc>http://unidata.github.io/awips2/cave/d2d-radar-tools/</loc>
-     <lastmod>2022-01-05</lastmod>
+     <lastmod>2022-01-11</lastmod>
      <changefreq>daily</changefreq>
     </url>
     <url>
      <loc>http://unidata.github.io/awips2/cave/d2d-edit-menus/</loc>
-     <lastmod>2022-01-05</lastmod>
+     <lastmod>2022-01-11</lastmod>
      <changefreq>daily</changefreq>
     </url>
     <url>
      <loc>http://unidata.github.io/awips2/cave/cave-localization/</loc>
-     <lastmod>2022-01-05</lastmod>
+     <lastmod>2022-01-11</lastmod>
      <changefreq>daily</changefreq>
     </url>
     <url>
      <loc>http://unidata.github.io/awips2/cave/import-export/</loc>
-     <lastmod>2022-01-05</lastmod>
+     <lastmod>2022-01-11</lastmod>
      <changefreq>daily</changefreq>
     </url>
     <url>
      <loc>http://unidata.github.io/awips2/install/start-edex/</loc>
-     <lastmod>2022-01-05</lastmod>
+     <lastmod>2022-01-11</lastmod>
      <changefreq>daily</changefreq>
     </url>
     <url>
      <loc>http://unidata.github.io/awips2/edex/settings/</loc>
-     <lastmod>2022-01-05</lastmod>
+     <lastmod>2022-01-11</lastmod>
      <changefreq>daily</changefreq>
     </url>
     <url>
      <loc>http://unidata.github.io/awips2/edex/distributed-computing/</loc>
-     <lastmod>2022-01-05</lastmod>
+     <lastmod>2022-01-11</lastmod>
      <changefreq>daily</changefreq>
     </url>
     <url>
      <loc>http://unidata.github.io/awips2/edex/edex-ingest-docker-container/</loc>
-     <lastmod>2022-01-05</lastmod>
+     <lastmod>2022-01-11</lastmod>
      <changefreq>daily</changefreq>
     </url>
     <url>
      <loc>http://unidata.github.io/awips2/edex/ldm/</loc>
-     <lastmod>2022-01-05</lastmod>
+     <lastmod>2022-01-11</lastmod>
      <changefreq>daily</changefreq>
     </url>
     <url>
      <loc>http://unidata.github.io/awips2/edex/data-distribution-files/</loc>
-     <lastmod>2022-01-05</lastmod>
+     <lastmod>2022-01-11</lastmod>
      <changefreq>daily</changefreq>
     </url>
     <url>
      <loc>http://unidata.github.io/awips2/edex/new-grid/</loc>
-     <lastmod>2022-01-05</lastmod>
+     <lastmod>2022-01-11</lastmod>
      <changefreq>daily</changefreq>
     </url>
     <url>
      <loc>http://unidata.github.io/awips2/edex/data-purge/</loc>
-     <lastmod>2022-01-05</lastmod>
+     <lastmod>2022-01-11</lastmod>
      <changefreq>daily</changefreq>
     </url>
     <url>
      <loc>http://unidata.github.io/awips2/edex/edex-users/</loc>
-     <lastmod>2022-01-05</lastmod>
+     <lastmod>2022-01-11</lastmod>
      <changefreq>daily</changefreq>
     </url>
     <url>
      <loc>http://unidata.github.io/awips2/edex/data-plugins/</loc>
-     <lastmod>2022-01-05</lastmod>
+     <lastmod>2022-01-11</lastmod>
      <changefreq>daily</changefreq>
     </url>
     <url>
      <loc>http://unidata.github.io/awips2/edex/case-studies/</loc>
-     <lastmod>2022-01-05</lastmod>
+     <lastmod>2022-01-11</lastmod>
      <changefreq>daily</changefreq>
     </url>
     <url>
      <loc>http://unidata.github.io/awips2/python/overview/</loc>
-     <lastmod>2022-01-05</lastmod>
+     <lastmod>2022-01-11</lastmod>
      <changefreq>daily</changefreq>
     </url>
     <url>
      <loc>http://unidata.github.io/awips2/appendix/educational-resources/</loc>
-     <lastmod>2022-01-05</lastmod>
+     <lastmod>2022-01-11</lastmod>
      <changefreq>daily</changefreq>
     </url>
     <url>
      <loc>http://unidata.github.io/awips2/dev/awips-development-environment/</loc>
-     <lastmod>2022-01-05</lastmod>
+     <lastmod>2022-01-11</lastmod>
      <changefreq>daily</changefreq>
     </url>
     <url>
      <loc>http://unidata.github.io/awips2/appendix/appendix-grid-parameters/</loc>
-     <lastmod>2022-01-05</lastmod>
+     <lastmod>2022-01-11</lastmod>
      <changefreq>daily</changefreq>
     </url>
     <url>
      <loc>http://unidata.github.io/awips2/python/maps-database/</loc>
-     <lastmod>2022-01-05</lastmod>
+     <lastmod>2022-01-11</lastmod>
      <changefreq>daily</changefreq>
     </url>
     <url>
      <loc>http://unidata.github.io/awips2/appendix/appendix-acronyms/</loc>
-     <lastmod>2022-01-05</lastmod>
+     <lastmod>2022-01-11</lastmod>
      <changefreq>daily</changefreq>
     </url>
     <url>
      <loc>http://unidata.github.io/awips2/appendix/appendix-wsr88d/</loc>
-     <lastmod>2022-01-05</lastmod>
+     <lastmod>2022-01-11</lastmod>
      <changefreq>daily</changefreq>
     </url>
     <url>
      <loc>http://unidata.github.io/awips2/cave/cave-keyboard-shortcuts/</loc>
-     <lastmod>2022-01-05</lastmod>
+     <lastmod>2022-01-11</lastmod>
      <changefreq>daily</changefreq>
     </url>
     <url>
      <loc>http://unidata.github.io/awips2/raytheon/cave_d2d/</loc>
-     <lastmod>2022-01-05</lastmod>
+     <lastmod>2022-01-11</lastmod>
      <changefreq>daily</changefreq>
     </url>
     <url>
      <loc>http://unidata.github.io/awips2/raytheon/smm/</loc>
-     <lastmod>2022-01-05</lastmod>
+     <lastmod>2022-01-11</lastmod>
      <changefreq>daily</changefreq>
     </url>
 </urlset>
\ No newline at end of file