System Requirements
amra runs on Microsoft Windows 2000/XP, Linux (Red Hat Enterprise Linux 3.0), Mac OS X Tiger (10.4), Sun Solaris 8 and 9, HP-UX 11.00, SGI Irix 6.5.x.
amira relies on fast hardware-accelerated OpenGL 3D graphics. We strongly recommend hardware texture mapping, since many visualization tools in amira rely on it. Hardware texture mapping is available, on all recent PC 3D graphics boards. On Unix systems it is available for example, on SGI O2, Octane and Onyx systems, on HP workstations with fx/4, fx/6 or fx/10 graphics, or on Sun Creator 3D, Elite, Expert 3D or newer graphics boards. For details on hardware acceleration, see below.
Apart from 3D graphics hardware probably, the most important system parameter is main memory. You should have at least 512 MB, preferably 2 GB or more. amira can also be started with less than 512 MB but it may decrease global performance.
The speed of the processor of course is also an important parameter. However it is less critical than the graphics system and the main memory size. For the PC versions, we recommend at least a 2 GHz processor.
On System Stability
amira is a very demanding application that extensively uses high-end features. Experience shows that such applications tend to reveal instabilities in system hardware, hardware drivers, and the operating system. A common problem is insufficient main memory. We recommend you configure enough swap memory in addition to physical memory. The total amount of virtual memory should be at least 1 GB. 2 GB would be even better.
Especially on PC platforms, OpenGL drivers today are often not as robust as desired. Also, system crashes due to bad memory chips or unstable power-supply are not rare. If you experience problems or instabilities with amira on your Windows platform, we recommend that you follow these steps:
If this does not help, or if a reproducible error occurs on different computers, then it might be a bug in the amira software itself. Please report such bugs so that they can be eliminated in the next release or a patch can be prepared.
Microsoft Windows
amira runs on Intel or AMD-based systems with Microsoft Windows 2000 and Microsoft Windows XP.
Graphics Hardware: You should use a graphics board with OpenGL support and texture mapping capabilities. Both is the case for almost all newer 3D boards.
Silicon Graphics
Graphics Hardware: To get optimal graphics performance, the machine should support texture mapping in hardware. Currently this is the case for all O2 systems, and for Octane systems with High Impact, Maximum Impact (not Solid Impact) and Odyssey graphics. amira provides a number of modules which make use of texture mapping, e.g., slicing, pseudo-coloring, or volume rendering. On machines without hardware texture mapping, these modules either run much slower or may not work at all. The advantage of the Octane is a higher speed in polygon rendering. For a complex model with an isosurface of 100,000 triangles, the frame rate is 10 per second for an Octane, compared to 3 per second for an O2. The MXE and MXI Octanes have larger texture memory than the SSE and SSI. Thus the MXE and MXI enable a direct volume rendering using 3D textures, which is not possible on an SE, SI or O2.
Software: The current version of amira requires IRIX 6.5.x or higher. We recommend you install the newest version of the operating system (see http://www.sgi.com/support).
HP-UX
amira performs pretty well on HP workstations equipped with Visualize fx/4, fx/6+, and fx/10 graphics cards under HP-UX 11.00. Probably it will run on other machines as well provided the OpenGL runtime environment has been installed. In any case we recommend to install the texture acceleration option for your graphics system (hardware texture mapping), especially if you intend to work with large 3D image data sets.
Important: By default some HP workstations are configured with a data size limit of 64 MB for each process. In order to load reasonable data sets, you should increase this value to 1 GB and the stack size to 128 MB. Do this by modifying the values in sam/Kernel Configuration maxdsiz=0x80000000, ssiz=0x8000000, tssiz=0x8000000.
SunOS
amira runs on Sun workstations with Solaris 8 or Solaris 9.
amira is successfully being used on systems with Creator 3D, Elite 3D, Expert 3D, and Zulu graphics boards. It runs on a simple Creator graphics boards as well. However, since no hardware texturing is available, performance is limited.
Linux
The Linux version of amira as been developed and tested on Red Hat Enterprise Linux 3.0. On other Linux distributions this version might not run because certain required system libraries are missing or because different versions of these libraries are installed.
There is also a version for Linux IA64 or AMD64 systems. This version has been compiled and tested on the Red Hat Enterprise Linux 3.0 distribution.
amira works with the current 3D graphics drivers from nVidia and ATI under XFree86 4/Xorg. It has also been successfully tested with other X-servers like the 3D Accelerated-X servers from XI graphics.
Note: After a standard installation of Red Hat Enterprise 3.0 Linux, hardware acceleration is not necessarily activated, although X-Windows and amira may work fine. To enable OpenGL hardware acceleration specific drivers may have to be installed, like the nVidia drivers from http://www.nvidia.com. This can increase rendering performance by an order of magnitude. Sometimes it is necessary to disable the stencil buffers (by starting amira with the option -no_stencils) to get acceleration.
Mac
The Mac version of amira has been developed and tested on Mac OS X Tiger (10.4). On other later Mac releases this version might not run because certain required system libraries may be different.
amira works with the current Mac 3D graphics drivers from nVidia and ATI.
In any case amira requires an X server resolution of at least 1024x768 and at least 15 bits of color depth. We strongly recommend 1280x1024 with 24-bit color depth at least.
Please note that if software rendering is used, rendering performance may drop significantly, especially for visualization techniques like volume rendering.