13. SOFTWARE REQUIREMENTS
The program is written in ANSI standard F95 with a few C language routines used to interface to the operating system. A serial mode Windows executable is included in the package; compilers are required on all other systems. PARTISN stresses most f95 compilers, so please ensure that the compiler version you are using is at least as recent as the one listed below on which the LANL developers ran the code system.
Lahey-Fujitsu LF95 Fortran Compiler Version 6.20 on Intel PC running Linux
PGI Fortran compiler version 7.2-5 on X86_64-linux
Intel Fortran Compiler Version 10.0.023 under Linux
Absoft 8.2 on Redhat Enterprise WS 3.0
Macintosh with Absoft
IBM XLF Fortran Compiler on IBM RS/6000
MIPSpro Fortran Compiler Version 184.108.40.206m on SGI
Compaq Fortran Compiler V5.5A.7 on Compaq Alpha under Digital Unix
Cray J90 and T90 with CF90 Version 220.127.116.11
Lahey-Fujitsu Fortran Compiler version 7.1 under Windows in a Cygwin environment
RSICC tested this release in serial mode under RHEL 4 Linux with Intel 10.1.015 and Portland Group Inc, 7.2-2. RSICC also built PARTISN on an Intel Core2 6600 in a Cygwin terminal under Windows Vista SP2 with the Lahey/Fujitsu Fortran 95 compiler Release 7.10.02. This 32-bit serial-mode Windows executable is included in the distribution
Parallelization is performed using MPI. Where available, POSIX routines are used to obtain the machine name, cross section path, and access rights. Otherwise, system-specific routines must be used. In addition to Fortran and C compilers, program building requires GNUmake (Version 3.74 or later), GNU awk (Version 3.0 or later), and CPP. A Readme file in the top program directory contains build instructions.
PARTISN is modularly structured in a form that separates the input and output (edit) functions from the main calculational (solver) section of the code. The code makes use of binary, sequential data files, called interface files, to transfer data between modules. Standard interface files whose specifications have been defined by the Reactor Physics Committee on Computer Code Coordination are accepted, used, and created by the code. A free-field card-image input capability is provided for the user. The code provides the user with considerable flexibility in using both card-image or sequential file input and in controlling the execution of modules.