December 6, 2014
The files in this directory are for installing the latest version 3.0.0 of AstroImageJ on Linux, Windows, and Mac operating systems. The files are complete and do not require a previous installation of ImageJ or AstroImageJ.
If you already have installed version 2.0 of AIJ, simply use the update option on the AIJ toolbar 'Help' menu to upgrade to 3.0.0. The user will need write permission to the directory where the software is installed.
For more information and help, please see the AstroImageJ user forum on nabble:
Once you have installed this version, use the Update feature under the Help menu to install the latest changes.
AstroImageJ_3.0.0_20141206_linux.tar.gz (provides AstroImageJ)
AstroImageJ_script.tar.gz (provides a startup script for AstroImageJ)
As root user
If you already have AstroImageJ installed in /usr/local change
it to a backup name such as
mv AstroImageJ AstroImageJ_old
Untar the archives
tar xvzf AstroImageJ_3.0.0_20141206_linux.tar.gz
Untar the script "astroimagej"
tar xvzf AstroImageJ_Script.tar.gz
Following the usual Linux convention, only lower case letters are used for the command line scripts. You may prefer to name it "aij" if you use the command line often, or as root in /usr/local/bin provide a soft link:
ln -s astroimagej aij
For Linux or other Unix installations note the recommended X11 resource change below.
Additional note about 64-bit Linux and 32-bit Linux
AstroImageJ will run with either the Sun or OpenJDK version 6 or higher of Java. For OpenSuse we find that the 13.1 default OS installation with OpenJDK 7 works fine.
Installing to older Linux systems with a 2.6 series kernel may fail for
large memory machines, especially if they have had a long uptime. In that case, if installing an up-to-date distribution is not an option, we recommend running AstroImageJ with the 32-bit JRE that is included in the ImageJ 32-bit package distributed by NIH.
Copy the 32-bit jre subdirectory from ImageJ to AstroImageJ and modify the astroimagej script in /usr/local/bin/ to
./jre/bin/java -Xmx3072m -jar ij.jar
The memory limitation with 32-bit java is less than 4 GB, and about 3 GB as shown is the maximum practical limit. With 64-bit java, the limit is
approximately 12 GB.
The KDE and Gnome window managers for recent distributions of Linux allow the user to control the double click timeout. However, they do not convey this to X11, so Java applications and many other programs that rely on X may default to a 200 millisecond timeout that is apparently too short. The solution is to add the following line to either /etc/X11/Xresources (the system wide default in OpenSuse) or on a user basis to .Xresources in each user's home directory:
! Local Modifications
The change will take effect after X is started the next time.