EnSight Installation Readme

The installation files for EnSight on the DAAC website are pre-configured with custom scripts that support HPC job launching. Special admin privileges are not required. The EnSight packages have also been configured to point to the EnSight CSI license server. Linux/Mac and Windows Instructions follow.

Linux/Mac Instructions

EnSight can be installed to any directory on your local workstation. Once extracted, sub-directories will be created that match the version numbers.

% cd  /desired/installation/dir
% tar -zxvf EnSight_10.2.5a_Lin.tgz
Environment Variables

You need to configure two environment variables as follows (depending on your shell):

For C Shell, add the following lines to the .cshrc file:

setenv CEI_HOME /path/to/CEI/##.#.#c
setenv PATH $CEI_HOME/bin:$PATH

For Bash Shell, add the following lines to the .bashrc file :

export CEI_HOME="/path/to/CEI/##.#.#c"
export PATH="$CEI_HOME/bin:$PATH"

(The text ##.#.#c above should be replaced to match the version directory, such as 10.0.3c or 10.1.2a.)

Launching EnSight

The command to start EnSight in client-server mode is:

% ceistart

Once launched, you may double click the remote host. Fill in the appropriate information (username, Project ID, local Kerberos ssh, etc) and click the Launch button. An EnSight job will be submitted to the queue. When the job starts running, a connection will be established to the remote system. The user parameters used for that connection will be saved for your next session to that server.

Windows Instructions

EnSight can be installed to * any directory on your local workstation. Once extracted, sub-directories will be created that match the version numbers

*NOTE: Zipped files are named in accordance with the OS to which they apply. By default, when a file is unzipped, it will create a base directory that matches the zipped filename. We suggest renaming the downloaded zipped file to simply CEI.zip, so that when it is extracted, the contents will be placed into the same CEI folder as previous versions. For example:

CEI/
   10.1.4b/
   10.1.6a/
   10.2.1b/
Environment Variables

You need to set up a %CEI_HOME% environment variable for the version of EnSight you wish to run. Startup batch scripts make extensive use of this CEI home location. You will also need to add the %CEI_HOME%/bin directory to the %PATH% environment variable. Open the Windows command prompt and type:

% setx  CEI_HOME  "c:\path\to\CEI\##.#.#c"
% setx  PATH  "%CEI_HOME%\bin;%PATH%

Where ##.#.#c above should be replaced to match the version directory, such as 10.1.2a or 10.2.1b.

Check that %CEI_HOME% was saved correctly by closing that command prompt and opening a new one. Type the following:

% set CEI_HOME

You should see the variable still set to the correct path.

Launching EnSight

The command to start EnSight in client-server mode is:

% ceistart.bat

Optionally, you may create a shortcut from the %CEI_HOME%\bin\ceistart101.bat file and place it on your desktop. With that done, you may launch EnSight by clicking that shortcut.

Once launched, you may double click the remote server machine. Fill in the appropriate information (username, Project ID, local Kerberos ssh command path, etc) and click the Launch button. An EnSight job will be submitted to the queue. When the job starts running, a connection will be established to the remote system. The user parameters used for that connection will be saved for your next session to that server.


Additional information on EnSight HPC job launching can be found at:

https://www.hpc.mil/images/hpcdocs/newsroom/hpcinsights_spring2011.pdf#page=12
https://dashboard.hpc.mil/movies/EnSightHPCJobLaunching/