VAPOR Binary Installation Documentation |
|
This document describes the VAPOR installation process for pre-compiled binaries on both UNIX and Windows systems. If you have not already done so, download an appropriate VAPOR image from the download site. Unless otherwise noted in the release notes below, pre-compiled binaries are built with compiler optimization enabled, IDL support turned on, and SGI Volumizer support turned off. Sites requiring a different configuration will need to build VAPOR from source code. OpenGL Graphics DriversFor best rendering performance it is imperative that hardware accelerated graphics are available on your system, and that an OpenGL driver, optimized for use with your graphics card, is installed. Under some operating systems, notably Linux, the hardware may be present, but the driver is absent (or misconfigured). The command below may be helpful on Linux systems for determining if your OpenGL driver is properly configured (look for the presence of either the nVidia or ATI vendor string, as appropriate for your hardware):
Note that Linux is notorius for uninstalling vendor-provided OpenGL drivers during OS upgrades Installing on UNIXThe binary installation process for UNIX is comprised of three basic steps: 1) unpacking the distribution image, 2) running the installation script, and 3) setting up the user environment. UnpackingUnpack the compressed tar file containing VAPOR into a scratch workspace (e.g. /tmp) and change working directories to the distribution subdirectory . The following commands might be used to unpack VAPOR version 1.0 on a Linux x86_64 system, for example:
InstallingNext, run the vapor-install.csh installation script providing a single argument informing the script of where to install VAPOR. For example the command
would install VAPOR executables, libraries, and examples in the directory /usr/local/apps/vapor-1.0.0 NOTE: The target of the vapor-install script ( /usr/local/apps/vapor-1.0.0, in the above example) must NOT be the same path as the directory where you unpacked the tar file or you will overwrite the installation image. User Environment SetupThe VAPOR suite of applications relies on a number of shared libraries. Unless VAPOR and all of its dependencies are installed in a directory known by the run time loader, users will be required to execute a configuration script prior to running any VAPOR commands. The script vapor_home/bin/vapor-setup.sh should be sourced by all users before starting a VAPOR session, where vapor_home is the the path to the VAPOR installation directory (/usr/local/apps/vapor-1.0 in our previous example) For convenience it is advised that users place this command in their login script (.login for C shell or .profile for other shells). Once the variables are set in the login script, there is no need to run the environment script files for each session. Installing on Max OS XOn the Mac OS X platform VAPOR is installed via a Mac installation package, delivered as a disk image. Installation is trivial:
User Environment SetupThe VAPOR installer on the Mac will permit the VAPOR application bundle to be installed wherever the user chooses. However, to facilitate access to command line utilities, symbolic links are created within /usr/local/{bin,lib} pointing to VAPOR executables and shared libraries within the application bundle. Thus the user's search path should contain /usr/local/bin. Similarly, users wishing to use VAPOR with IDL will need to set the IDL_DLM_PATH and DYLD_LIBARARY_PATH environment variables to /usr/local/lib. As a convenience, users may simply source the /usr/local/bin/vapor-setup.csh script (/usr/local/bin/vapor-setup.sh for bourne shell users).
Installing on WindowsIf you have previously installed VAPOR (version 1.0.x) on your Windows system, you should delete that installation (versions 1.0.x did not use an uninstaller) as follows:
Next, to install VAPOR:
You can launch the VAPOR user interface by double-clicking on the vaporgui
Platform Specific Installation NotesVersion 1.2.2Windows VistaWhile installing on Vista, User Account Control (UAC) should be temporarily disabled. Version 1.0.0Linux_ia64Linux_ia64 binaries are compiled without IDL support. At this time RSI does not offer IDL on the Intel IA64 platform. You may of course run Linux_i386 binaries with IDL support on IA64 platforms, albeit with degraded performance and limited memory.
|
|