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 Ansys 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_{version}_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/{version}
setenv PATH $CEI_HOME/bin:$PATH

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

export CEI_HOME="/path/to/CEI/{version}"
export PATH="$CEI_HOME/bin:$PATH"

{version} may be of the older CEI format of ##.#.#c or the newer Ansys format of YYYYR#. In late 2019, Ansys changed the version-naming template to YYYYR#, such as 2019R1. They aim to release three versions per year.

Launching EnSight

The command to start EnSight for client-server sessions is:

% ceistart

Once launched, you may 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 zip files can be extracted to any directory on your local workstation where you have write access. No admin privileges are required; nothing is written to the registry keys. Once extracted, a sub-directory will be created that matches the version numbers. This is the correct directory to match the %CEI_HOME% environment variable.

Environment Variables

You need to set up a %CEI_HOME% environment variable for EnSight to run correctly, or create a shortcut on the desktop that directly points to %CEI_HOME%\bin\ceistart.bat. For the former option, open the Windows command prompt and type:

% setx  CEI_HOME  "c:\path\to\CEI\{version}"
% setx  PATH "%CEI_HOME%\bin;%PATH%"

{version} may be of the older CEI format of ##.#.#c or the newer Ansys format of YYYYR#. In late 2019, Ansys changed the version-naming template to YYYYR#, such as 2019R1. They aim to release three versions per year.

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 for client-server sessions is:

% ceistart.bat

Once launched, you may click the remote host, 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/private/DAAC/movies/EnSightHPCJobLaunching/