13. SOFTWARE REQUIREMENTS
The program is written in ANSI standard F90 with a few C language routines used to interface to the operating system. No executables are included in the package, so compilers are required on all systems. PARTISN stresses most f90 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
- Absoft 8.2 on Redhat Enterprise WS 3.0
- IBM XLF Fortran Compiler Version 7.1.0.3 on IBM RS/6000
- MIPSpro Fortran Compiler Version 7.3.1.3m on SGI
- Compaq Fortran Compiler V5.5.0 1 on Compaq Alpha under Digital Unix
- Cray J90 and T90 with CF90 Version 3.0.2.1
- Lahey-Fujitsu Fortran Compiler version 7.1 under Windows in a Cygwin environment
RSICC tested this release in serial mode on IBM RS/6000 under AIX 5.1 with XL Fortran 08.01.0000.0003 and on a Pentium IV running WindowsXP SP2 with Lahey/Fujitsu Fortran 95 Compiler Release 7.10.02 and in parallel and serial modes on AMD Athlon with Lahey/Fujitsu Fortran 95 L6.10a under Red Hat Linux 7.3.
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.