Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "Getting ICE"

(HDF5)
(HDF5)
Line 7: Line 7:
 
=== HDF5 ===
 
=== HDF5 ===
  
ICE requires the HDF5 native and Java libraries installed locally to use the ''ReactorAnalyzer'' tools. Note that the HDF5 and HDF-Java libraries ''must'' be included in your system's <tt>PATH</tt> variable. For example, for HDF libraries installed on Windows in the default locations, the following paths would need to be added to the <tt>%PATH%</tt> variable:
+
ICE requires the native HDF5 and HDF-Java libraries installed locally to use the ''ReactorAnalyzer'' tools. We recommend installing the pre-built binaries. At the time of writing this, the HDF-Java libraries are bundled together with HDF-View, a Java-based browser for HDF files. We may use the terms "HDF-View" and "HDF-Java" interchangeably, but know that they are one and the same.
 +
 
 +
Note that on Windows, the HDF5 and HDF-Java libraries ''must'' be included in your system's <tt>%PATH%</tt> variable. For example, for HDF libraries installed in the default locations, the following paths would need to be added to the <tt>%PATH%</tt> variable:
 
<pre>
 
<pre>
 
C:\Program Files\HDF_Group\HDF5\1.8.14\lib
 
C:\Program Files\HDF_Group\HDF5\1.8.14\lib
 
C:\Program Files\HDF_Group\HDFView\2.10.1\lib
 
C:\Program Files\HDF_Group\HDFView\2.10.1\lib
 
</pre>
 
</pre>
 +
 +
For Unix-like systems, configuring HDF libraries requires a little bit more jiggery-pokery. It is not sufficient to just add the HDF5 and HDF-Java libraries to your <tt>ld.so.config</tt> file. They must be added to your <tt>LD_LIBRARY_PATH</tt> variable. If you do not know how to do this, you can run the following script from your home directory and replace <tt><path_to_hdfview-libs></tt> and <tt><path-to-hdf5-libs></tt> 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 <tt>~/.bashrc</tt> file.
 +
<pre>
 +
cp .bashrc .bashrc.backup
 +
echo "LD_LIBRARY_PATH"=<path_to_hdfview-libs>:<path-to-hdf5-libs>:$LD_LIBRARY_PATH
 +
export LD_LIBRARY_PATH
 +
</pre>
 +
For example, if your HDF5 libraries are stored in <tt>/opt/hdf5</tt> and your HDF-Java libraries are in your </tt>/home</tt> directory, the script would be as follows:
 +
<pre>
 +
cp .bashrc .bashrc.backup
 +
echo "LD_LIBRARY_PATH"=$HOME/hdfview/lib/linux:/opt/hdf5/lib:$LD_LIBRARY_PATH
 +
export LD_LIBRARY_PATH
 +
</pre>
 +
If you make a mistake, you can restore your old <tt>~/.bashrc</tt> by replacing <tt>.bashrc</tt> with <tt>.bashrc.backup</tt> that was created by the script.
 +
In addition to this, you may need to add these files in your <tt>ld.so.conf</tt> file. Speak to your system administrator if you do not know how to do this.
  
 
=== VisIt ===
 
=== VisIt ===

Revision as of 18:18, 6 January 2015

This page describes the process by which users can download and use the binary version of ICE. We recommend most users use the binary, however, for those who are adventurous at heart, detailed instructions on building ICE from the source code are available on the ICE Build Instructions page.

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. Some tools in ICE also require the installation of third-party libraries. While it's not necessary to install these libraries to run ICE, the Reactors and Visualization perspectives will not work correctly without them. ICE assumes these third party libraries are located in the default installation directories; see the Tips and Tricks section for dealing with installations in non-default locations.

HDF5

ICE requires the native HDF5 and HDF-Java libraries installed locally to use the ReactorAnalyzer tools. We recommend installing the pre-built binaries. At the time of writing this, the HDF-Java libraries are bundled together with HDF-View, a Java-based browser for HDF files. We may use the terms "HDF-View" and "HDF-Java" interchangeably, but know that they are one and the same.

Note that on Windows, the HDF5 and HDF-Java libraries must be included in your system's %PATH% variable. For example, for HDF libraries installed in the default locations, the following paths would need to be added to the %PATH% variable:

C:\Program Files\HDF_Group\HDF5\1.8.14\lib
C:\Program Files\HDF_Group\HDFView\2.10.1\lib

For Unix-like systems, configuring HDF libraries requires a little bit more jiggery-pokery. It is not sufficient to just add the HDF5 and HDF-Java libraries to your ld.so.config 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

For example, if your HDF5 libraries are stored in /opt/hdf5 and your HDF-Java libraries are in your </tt>/home</tt> directory, the script would be as follows:

cp .bashrc .bashrc.backup 
echo "LD_LIBRARY_PATH"=$HOME/hdfview/lib/linux:/opt/hdf5/lib:$LD_LIBRARY_PATH 
export 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 ld.so.conf file. Speak to your system administrator if you do not know how to do this.

VisIt

ICE requires VisIt 2.8.2 be installed on a local or remote machine to use the VisIt Viewer tool.

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.

Downloading ICE

Our binary build is temporarily unavailable here. If you'd like to obtain the binary version of ICE, please contact us at ice-dev <at> eclipse.org


The latest stable version of ICE is version 2.1.6. The binary distribution is a fully-functional, full-featured, executable version of ICE that includes everything except for the Java Virtual Machine, third-party libraries and plug-ins currently in development.

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. For example, ICE2.1.6-win32.win32.x86_64.zip is ICE version 2.1.6 for 64-bit Windows. The choices are as follows:

Binary version Operating System
ICE2.x.y-win32.win32.x86_64.zip 64-bit versions of Windows, including most installations of Windows Vista, 7 and 8
ICE2.x.y-win32.win32.x86.zip 32-bit versions of Windows, including most installations of Windows XP
ICE2.x.y-macosx.cocoa.x86_64.zip 64-bit Mac, including most OS X installations (10.4.7 "Tiger" and newer)
ICE2.x.y-macos.cocoa.x86.zip 32-bit Mac, including some OS X installations (10.4.4 "Tiger" to 10.6.8 "Snow Leopard")
ICE2.x.y-linux.gtk.x86_64.zip 64-bit Linux running GTK (most flavors of Linux)
ICE2.x.y-linux.gtk.x86.zip 32-bit Linux running GTK

On a 64-bit installation of Red Hat Enterprise Linux 6 (RHEL6), the ICE.product-linux.gtk.x86_64.zip version of ICE is the appropriate choice.

Running ICE

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

Windows
In the file browser, navigate to the folder where you extracted ICE. 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.
Macs
You may get a message that says that ICE is from an unidentified developer and cannot be opened. In the file browser, you can right-click the executable, click "Open" in the menu that appears and then click "OK" when prompted again. Alternatively, ICE may be executed from the command line on Linux and Mac systems.
Linux
ICE may be executed from the command line on Linux systems by navigating to the folder where ICE was extracted, and then issuing the command ./ICE.

When ICE runs, it will stream data to a console window that displays debug information as the environment is used. You may safely ignore this window while you are working by keeping it minimized or in the background.

What if ICE fails to run?

If ICE fails to run, email us directly at ice-dev <at> eclipse.org. If you believe that you have identified a bug, please report it to our bug tracker.

Tips and Tricks

Back to the top