Installing the Application Distributions

• Installing on a UNIX System
  • Variation for NFS Users
• Installing on a Windows System

Installing on a UNIX System

It is suggested that one individual from an organization download the needed application distributions and be a single point of contact for the WIND software. If possible, the executables should be located in a central location that can be accessed via NFS in a consistent manner. This way, the location and method of accessing the code will be the same on all user machines, and the code can be updated without impacting the user significantly.

After downloading the gzip'ed tar files containing the application and tools distributions for the platforms to be used, the recommended installation procedure is as follows:

1. If previous versions of WIND and/or the WIND tools have been installed on the system, rename the old CFDROOT and TOOLSROOT directories (the directories themselves, that is, not the CFDROOT and TOOLSROOT environment variables), and check to be sure that these directories are not in your search path. [For those of you asking "Why?" - this will ensure that the new versions of the scripts can be properly installed, and that the new version of pvmgetarg will be used to determine the SYSTEM and SYSTEM_CPU environment variables. After the installation of the new version has been completed, earlier version(s) of WIND may be removed, or copied to the newly-installed bin directory under a different name.]
   
   
2. Put the gzip'ed tar files containing the WIND and tools application distributions into an appropriate directory, such as wind. This directory does not have to be the permanent parent directory for the scripts and executables, but it can be.
   
   
3. In that directory, unpack the files by doing, for both files:

      gunzip -c filename | tar xvf -

   where filename is the file name, including the .tar.gz extension. If application distributions were downloaded for several different machines, all of the gzip'ed tar files should be unpacked before proceeding to the next step.
   
   
4. Run the INSTALL.appl script. You'll be prompted for the directory into which the WIND scripts and executables should be placed. As noted above, it's convenient to create and use a directory that multiple users can access via NFS. The files will be copied into a wind subdirectory directly below the directory you specify. For example, responding with /usr/local/wind will result in all the scripts and executables being copied into /usr/local/wind/wind.

   If the scripts and executables are to be kept under the original directory used for the gzip'ed tar files in Step 2, simply respond to the prompt with "." (without the quotes).

   The INSTALL.appl script will not modify any of your system or user configuration files. It simply copies the appropriate files to the directory you specify. It also modifies two files included with the WIND application distribution - cfd.login and cfd.profile - to define the environment variable CFDROOT as the full path name of the directory specified above.
   
   

5. Run the Install.tools script. This step is exactly analogous to the one above, and is used to install the scripts and executables for the various pre- and post-processing tools used with WIND. The installation directory should be the same as specified in the previous step. The files will be copied into a tools subdirectory directly below the specified directory.

   As before, to keep the tools scripts and executables under the original directory used for the gzip'ed tar files in Step 2, simply respond to the prompt with "." (without the quotes).

   As in Step 4, the Install.tools script modifies two files included with the tools application distribution - tools.login and tools.profile - to define the environment variable TOOLSROOT.

While that completes the actual installation of the WIND and tools application distributions, users must perform one additional step. csh and tcsh users should add the following two lines to their .login file in their home directory:

   source dir_name/wind/bin/cfd.login
   source dir_name/tools/bin/tools.login

   . dir_name/wind/bin/cfd.profile
   . dir_name/tools/bin/tools.profile

Note that, to run WIND or any of the tools immediately after completing the above process, you (and any other users currently logged on) should logout and log back in to execute the .login or .profile file, setting some environment variables, including CFDROOT, SYSTEM, and SYSTEM_CPU, and modifying the PATH environment variable to include the newly-created locations for the WIND and tools executables. Alternatively, csh and tcsh users could execute

   source .login

   . .profile

Variation for NFS Users

When the scripts and executables are to be accessed via NFS, if the path name used by the user to access the NFS-mounted file system is different from the actual directory name on the "central" system, a slight variation of the above procedure is necessary. The definitions of the environment variables CFDROOT and TOOLSROOT in the cfd.login, etc., files on the central system should be modified to point to the NFS-mounted location of the wind and tools subdirectories. Similarly, the lines users add to their .login or .profile files should specify path names used to access the NFS-mounted file system.

For example, at NASA Glenn automount is normally used to access NFS file systems. The WIND and tools application distributions are stored on a central workstation (named, say, wind_machine), in the directory dir_name as specified in Step 4 of the previous section. This directory is exported read-only to the "home" system, normally an individual's workstation, for each WIND user.

The cfd.login, etc., files on wind_machine were copied to new files called cfd.nfs.login, etc. [This was done so that users logging directly onto wind_machine could still access WIND as described in the previous section.] The definitions of CFDROOT and TOOLSROOT in cfd.nfs.login, etc., were modified to point to the automount'ed location of the wind and tools subdirectories. E.g., if dir_name is /usr/local/wind, then the user automounts the wind directory by typing

   cd /net/wind_machine/usr/local/wind

Finally, using the above example, csh and tcsh users modify their .login file to add the lines

   source /net/wind_machine/usr/local/wind/wind/bin/cfd.nfs.login
   source /net/wind_machine/usr/local/wind/tools/bin/tools.nfs.login

   . /net/wind_machine/usr/local/wind/wind/bin/cfd.nfs.profile
   . /net/wind_machine/usr/local/wind/tools/bin/tools.nfs.profile

As in the previous section, to run WIND or any of the tools immediately after adding these lines, users currently logged on should logout and log back in to execute the .login or .profile file, setting the CFDROOT and TOOLSROOT environment variables. Alternatively, csh and tcsh users could execute

   source .login

   . .profile

Installing on a Windows System

Unfortunately, due to resource limitations, the NPARC Alliance cannot officially support a Windows version of WIND. Nevertheless, application distributions for Windows may be available for WIND and some of the tools. These executables will generally not be as current as those in the supported Unix versions. The recommended installation procedure for Windows application distributions is described below.

After downloading the gzip'ed tar files containing the WIND and tools application distributions to some temporary directory:

1. Uncompress the gzip'ed tar file using some appropriate decompression software, such as WinZIP, extracting all the files into the temporary directory. With WinZIP this is done by clicking on the "Extract" button.
   
   
2. An "Install" link will appear in the temporary directory. Double click this to install the code(s). A DOS window will open.
   
   
3. Specify where you want to install the code(s) and a default name for the location for running applications. The applications directory is just the default and can be changed interactively later.
   
   
4. Follow the instructions regarding modification of the autoexec.bat file, then reboot.

An icon should appear on your desktop. Double-clicking on it will start execution of the WIND code.