Download fv

fv is built as a standard part of the FTOOLS distribution for release 3.6 and higher, or you can get the latest standalone version from our ftp site...

Each of the following distributions contains several sample FITS files on which users can explore fv's capabilities. Several sample scripts are also included.

If you experience problems using FTP to download this software, click here

Unix users should download the tar file appropriate for their platform:

Mac OSX/Darwin,

Solaris,

OSF,

PC Linux ,

Mac Linux,

These links will retrieve a gzipped tar file (roughly 2.6 to 2.8 Meg in size). To unpack the file, type:

   > gunzip -c fv40_<ARCH>.tar.gz | tar xf -

where <ARCH> depends on the file downloaded. This will create an fv4.0 directory containing a platform-specific directory (pre-compiled binaries and libraries used by fv), associated documentation, sample data, and sample scripts. Once unpacked, fv can be run immediately; just type ./fv in the fv4.0 directory. Everything you need is contained in each tar file.

Windows users should download the lastest executable (11.1 Meg). Once you've downloaded the file, double-click on it to launch InstallShield, which will guide you through the installation process. The new Windows version also features the ability (as UNIX's) to print and save images in the POW display window.

Mac OS (except for Mac OS X) users should download fv 3.0 executable (1.9 Meg). Decompress the file and run fv. An included AppleScript can be used to set files' Creator/File types so that they will be opened by fv when double-clicked. Use the "File Exchange" control panel to have the ".fits" (and other) filename extension(s) recognized as being a fv FITS file when moving files to your computer from PCs or downloading them from the internet. More details can be found in an included README file.

NOTE TO HEASOFT USERS: If you want to replace the fv in your HEASOFT distribution with the newest version of fv, simply move (or copy) the contents of the untarred fv4.0/ directory into the $LHEASOFT/bin/ directory. You may want to move aside the existing $LHEASOFT/bin/fv to e.g. $LHEASOFT/bin/fv31 first since you will be copying in a new fv executable.