Installing FISPACT-II

FISPACT-II has been installed on various platforms and clusters around the world. Pre-compiled executables are supplied for several operating systems and compilers in the standard distributions. If you are unable to find a executable for your system, please post your details on the FISPACT-II forum or contact the project members directly.

*NIX installation

For those using a Linux, Unix or OSX system without a current version of FISPACT-II, a short guide for new installations is outlined below. We will assume that the user is installing the code in a homespace from some media directory.

Within your installation directory copy the full FISPACT-II media content and uncompress all tar.bz2 files with the provided uncompress script

mkdir ~/FISPACT-II
cd ~/FISPACT-II/
cp -R /media/FISPACT-II/ .
chmod -R u+w *
chmod +x libdatauncompress
./libdatauncompress

or directly

cd ENDFdata/
tar -xjvf decay.tar.bz2
rm decay.tar.bz2
tar -xjvf ...

Note that the full nuclear data files provided in FISPACT-II will require, when expanded, more than 40 Gb disc space. The QA suite can then be uncompressed, requiring around 1 Gb in total

chmod +x fispQAuncompress
./fispQAuncompress

Users who require source code access may request this directly from the UKAEA nuclear data manager, but FISPACT-II executables are provided for numerous operating systems with different compilers. For the following, we will take the ifort compiled executable for a 64-bit Linux system. Either copy the executable to your bin or produce a sybolic link

cd ~/bin
cp ~/FISPACT-II/fispact/exec/Linux/64-bit/ifort/fispact .

or

cd ~/bin
ln -s ~/FISPACT-II/fispact/exec/Linux/64-bit/ifort/fispact 

The set of QA tests will require an environment variable which points to the executable that has now been installed in /bin/

fispact=~/bin/fispact; export fispact

To run the test QA cases, master scripts have been privided which execute simulations within fispQA and fispQA2012, which can be initialised with

./runalltests your.times >& your.log

which will output the runtimes for the cases and terminal log. The QA folders also contain testresults/ folders which provide references for each case. Simply running

diff test81.out testresults/.

should identify any problems. Note that different compiler versions of the code may give minor numberical differences and that some test cases are specifically designed to give errors or warning messages.