Last version:
FLUKA 2011.2c.5, October 15th 2016
(last respin )
flair-2.2-5 23-Nov-2016

News:

Next Course
( 19.01.2017 )

The 19th FLUKA Beginners Course will be held at the Pohang Accelerator Laboratory (PAL), POSTECH, South Korea, May 8-12, 2017.


[   Manuals  |  Online Manual  |  Ascii Manual  |  pdf Manual  |  Presentations  |  Publications  |  Citations  |  Install and Run  |  Examples  |  FAQ  |  Readme  |  License  |  LicensePreamble   |  Release notes   ]

font_small font_med font_big print_ascii

To install FLUKA about 500 Mbyte of disk space are needed. In addition, a FORTRAN compiler suitable for your platform is required to generate the FLUKA executable(s). Different packages can be downloaded from the FLUKA Website www.fluka.org:

  • 32 bits, requires gcc/g77 (version >= 3.4)
    • linux x86 (tar.gz package): fluka20[xx].[y]-linuxAA.tar.gz
    • linux x86 (rpm installer):fluka20[xx].[y]-i686.rpm
  • 64 bits, requires gcc/gfortran (version >= 4.6)
    • Linux x86_64 (tar.gz package):fluka20[xx].[y]-linux-gfor64bitAA.tar.gz
  • Virtual machine, for Windows PC
    • FLUPIX iso image:flupix20[xx].[y]-flair.iso
    • instructions for installation here>

The Linux x86 version must be compiled at 32 bits with g77 but can run on both 32 and 64 bit machines while the Linux x86_64 version must be compiled with gfortran and works only on 64 bits machine. The latter is still tentative, we cannot exclude some issues with that version. The code has been checked and validated for these platforms/compilers only for the time being.



Installation of the tar.gz packages
  1. The user must defines few environmental variables:
    • FLUPRO: pointing to the directory where the distribution tar file will be decompressed. If you work on bash do:
       > export FLUPRO=/pathto/fluka 
      or if you work on csh or tcsh do:
       > setenv FLUPRO /pathto/fluka 

      If the directory does not exist you should first create it by:
      > mkdir /pathto/fluka

    • FLUFOR (optional): containing the compiler type (gfortran or g77) which must be coherent with the architecture of the package you downloaded.
      If you work on bash do:
      > export FLUFOR=g77 
      or
      > export FLUFOR=gfortran

      while if you work on csh or tcsh do:
      > setenv FLUFOR g77
      or
      > setenv FLUFOR gfortran
      In case FLUFOR is not set the script does an attempt of checking if the name of the $FLUPRO directory contains the gfor string. In this case gfortran is selected. If the FLUFOR variable is not set and the compiler platform name is not coded in the directory name g77 is selected.

    • GFORFLU (optional): set to specify the specific version of gfortran to be used if more than one is available (i.e. if on your machine gfortran points to a version < 4.6, and gfortran46 points to version 4.6, you can set GFORFLU to gfortran46 and happily use the FLUKA gfortran 64 bits version).

    Note: Such definition of the environment variables are lost when you log out. In order to make it permanently available you should add the export/setenv command to your shell configuration file:
    • If you work on bash add them to your .bashrc file;
    • If you work on csh (or tcsh) add them to your .cshrc (or .tcshrc) fill

  2. Go to the FLUPRO directory and move there the selected FLUKA package
     > cd $FLUPRO
    then
     > cp /path/fluka2011.2b-linuxAA.tar.gz ./
    or
     > cp /path/fluka2011.2b-linux-gfor64bitAA.tar.gz ./
  3. Uncompress the tar.gz the package
     > tar -zxvf fluka2011.2b-linuxAA.tar.gz
    or
     > tar -zxvf fluka2011.2b-linux-gfor64bitAA.tar.gz
  4. Compile the flutils, link and install FLUKA by typing:
     > make
    this creates the default executable flukahp and compiles auxiliary programs in the directory flutil.



In order to be able to perform nucleus-nucleus interactions, a special executable linking the event generator libraries already included in the distributed package, is needed. To create it, the script ldpmqmd in $FLUPRO/flutil has to be launched:

		$FLUPRO/flutil/ldpmqmd
	

The default name of the executable coming out is flukadpm3. You can set a different name through the option - o. This is useful when linking in addition one's own user routines. A list of options supported by the script lfluka (internally used by ldpmqmd) is shown issuing the command

		$FLUPRO/flutil/lfluka -h
	

Note that the twin script ldpm2qmd allows to link a previous version of the DPMJET event generator (DPMJET-2.53 instead of DPMJET-3).



In order to run FLUKA, one has to prepare an input file (e.g. myproblem.inp) looking like the examples available in the $FLUPRO directory. It is recommended to work/run in a directory different from the installation one, i.e. outside $FLUPRO. Detailed instructions for building a FLUKA input can be found in the Section 2.2 of the Manual. The run is started launching the script rfluka

		$FLUPRO/flutil/rfluka myproblem [without ".inp"]
	

The standard executable $FLUPRO/flukahp will be used. A different executable to be used can be specified through the option - e. A list of options supported by the script rfluka is shown issuing the command

		$FLUPRO/flutil/rfluka -h
	

A lecture focused on installing and running FLUKA is provided as a part of the user course material (Installation, Release Notes).

With the FLUKA package, you received a current version of the FLUKA manual. The manual is the major source of information/help for preparing and running FLUKA. It is available also online.

Take a look also at the RELEASE-NOTES.

Always a good way to get started with a new software tool is to study well documented examples. We are trying to provide a series of such examples for various physics conditions.

Last updated: 23rd of April, 2015

© FLUKA Team 2000–2017

Informativa cookies