Skip to main content
Jump to: navigation, search

Getting ICE

Revision as of 14:36, 4 December 2014 by (Talk | contribs) (Created page with "This page describes the process by which users can download and use ICE. Detailed instructions on building ICE are available on the [Compiling ICE From Scratch page](Compiling...")

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

This page describes the process by which users can download and use ICE. Detailed instructions on building ICE are available on the [Compiling ICE From Scratch page](Compiling ICE From Scratch).

    • Table of Contents**


    1. Prerequisites

ICE requires Java 1.6 or greater. Sun's version of Java can be used on Linux, Windows or Mac and the OpenJDK can also be used Linux and Mac. The ICE Development Team prefers the OpenJDK on Linux systems.

ICE should work out-of-the-box with no problems if the following third party libraries are installed to their default locations. See the "tips and tricks" section for dealing with custom install locations.

      1. Sample Data

If you want to download some sample data to play around with different features of ICE, it is available [here]().

      1. VisIt

[VisIt]( is an optional requirement for those who want to use the Reactor Analysis Tool, which requires VisIt 2.5.2. Download the appropriate version of VisIt for your machine and extract it to a folder called "visit" in your home directory. VisIt should be run at least once before using ICE to make sure it works on your system.

      1. HDF5

[HDF5]( is required if you intend to use the ICE ReactorAnalysis tools. If you will not be using the ReactorAnalysis tools, installing HDF5 is not required. You will need both HDFView and the binaries. As of the latest release, these are installed [together.]( Make sure that you install the proper versions of both for your architecture. The HDF5 Java and C libraries must be on your path.

      1. 3D Graphics

ICE also requires that your system has 3D rendering enabled to edit geometries, which is normally done by installing the 3d graphics drivers from the vendor of your graphics card. You should consult your IT specialist if you do not know how to enable this on your own.

Please note that some of the above packages may be optional for running the binary version of ICE, but if you are one of the brave souls trying to build ICE from scratch all of the above packages are **required.**

    1. Downloading ICE

ICEFilesPage 20120924.png

Binary distributions of ICE are available [here](), which is also depicted in the thumbnail image to the right. The latest stable version of ICE is version 2.1.5. The binary distribution is a fully-functional, full-featured, executable version of ICE that includes everything except for the Java Virtual Machine, VisIt and plug-ins currently in development.

The "files" folder contains several subfolders and extra files. You should select the appropriate file named ICE2.x.y-*.zip where the * is the correct operating system and processor architecture for your system and x and y are major and minor version numbers. The choices are as follows:

 * - ICE for 64bit versions of Windows, including Windows 7. 
 * - ICE for 32bit versions of Windows, including most installs of Windows XP. 
 * - ICE for 64bit Mac, including OS/X. 
 * - ICE for 32bit Mac. 
 * - ICE for 64bit Linux running GTK. (Most flavors of Linux.) 
 * - ICE for 32bit Linux running GTK. (Most 32bit installs of Linux.) 

On a 64bit installation of Red Hat Enterprise Linux 6 (RHEL6), the ICE.product-linux.gtk.x86_64 version of ICE is the appropriate choice. For Windows 7, should be selected.

    1. Running ICE

Once you download the appropriate zip file for your computer, unzip it to a directory of your choice. No additional installation steps are required because ICE is executed directly from this directory.

    • On a Mac** you might get a message that says that ICE is from an unidentified developer and cannot be opened. You can simple right-click the executable, click "Open" in the menu that appears and then click "OK" when prompted again.
    • On Windows,** navigate to the folder where you installed ICE and in the ICE folder, double-click ICE.exe. On Linux and Mac systems, you may follow the same procedure, but the ICE executable is only called "ICE" on those systems. Alternatively for Linux and Mac systems you may execute ICE from the shell.

ICE will open a console that displays debug information and allows for expert debugging in addition to the user interface for your interactions. You may safely ignore this window while you are working.

    1. What do I do if ICE fails to run?

If ICE fails to run, you should send an email to billingsjj <at> ornl <dot> gov. If you believe that you have identified a bug, please report it to [our bug tracker](

    1. Install Problems: Tips & Tricks

The following tips are all about modifying the ICE.ini file to invoke special behavior. There is one very important thing to keep in mind about the INI files on Windows: make sure you put your new "-D" options on their own line!

      1. VisIt

The VisIt binary executable path should point to the directory that contains visit/visit.exe if it is not on the system path. This can be configured in the ICE.ini file using something like: -Dvisit.binpath=C:\Program Files\LLNL\VisIt 2.5.2

The ICE Development Team prefers to install VisIt in a system location and then use symbolic links to our home directories, as such:

 * On Linux from /home/yourUsername, "ln -s visit-2.5.2/ visit" 
 * On Mac from /Users/yourUsername, "ln -s /Applications/ visit" 
      1. HDF5

On Linux machines it is not sufficient to add the HDF5 and HDFView libraries to your file. They must be added to your "LD_LIBRARY_PATH" variable. If you do not know how to do this, you can run the following script from your home directory and replace <path_to_hdfview-libs> and <path-to-hdf5-libs> to your library directories for those packages as appropriate. The first part of this script backs up your current configuration and the second part appends the necessary variables to your .bashrc file.

   cp .bashrc .bashrc.backup
   echo "LD_LIBRARY_PATH"=<path_to_hdfview-libs>:<path-to-hdf5-libs>:$LD_LIBRARY_PATH 
   export LD_LIBRARY_PATH 

If your HDF5 libraries are stored in /opt/hdf5 and your hdfview libraries are in your home directory this would look like

   cp .bashrc .bashrc.backup 
   echo "LD_LIBRARY_PATH"=$HOME/hdfview/lib/linux:/opt/hdf5/lib:$LD_LIBRARY_PATH 

If you make a mistake, you can restore your old .bashrc by replacing .bashrc with .bashrc.backup that was created by the script.

In addition to this, you may need to add these files in your file. Speak to your system administrator if you do not know how to do this.

The location of the HDFView package can also be specified with the java.library.path option in the ICE.ini file, although this may prevent access to other system libraries. For example: -Djava.library.path=C:\Users\My Username\hdfview\lib\win -Djava.library.path=/home/myUsername/hdfview/lib/linux

Some Windows configurations, particularly those where HDFView is installed in user land, may fail to load the hdf-java DLL files in hdfview\lib\win even if they can be found. In some cases ICE will throw a Java exception that says "UnsatisfiedLinkError: Access is denied." This can be fixed by granting the HDFView libraries 'Full Control' access rights for your user, as show below, by right-clicking on the DLL and selecting "Properties." This should be done for both jhdf5.dll and jhdf.dll.


Back to the top