2.4} Running FLUKA

 ---------------------
 It is advisable, but not mandatory, to keep separate the $FLUPRO directory
 from that or those where calculations are run and input files are kept.
 For instance, flukawork:

  cd /home/user/flukawork

 As mentioned above, the rfluka script in $FLUPRO/flutil should be used to
 drive the FLUKA run. In the following it is supposed that the user is going
 to ask for five statistically independent runs, each one made of 100000
 histories, of the proposed basic example. The command is:

  $FLUPRO/flutil/rfluka -N0 -M5 example &

 (on LINUX/UNIX, the & character allows to run the program in the background
 without "freezing" the terminal window).

 The script creates a temporary subdirectory called fluka_nnnn where nnnn is
 tbe number of the subprocess. For instance, when the first run (or "cycle")
 starts, the user will see on the terminal lines similar to the following
 ones:

  $TARGET_MACHINE = Linux
  $FLUPRO = /home/user/flupro
  2789: old priority 0, new priority 10

  Initial seed already existing

  Running fluka in /home/user/flukawork/fluka_2789

  ================================ Running FLUKA for cycle # 1 ===================

 At the end of each cycle the output files will be copied onto the running
 directory, the temporary directory will be erased and a new one will be
 created where the next run will take place. The names of the output files
 from each run are built by appending to the input file name the run number
 and an extension depending on their content: .out for the standard output,
 .err for the error file, .log for the log file and _fort.nn for the estimator
 files (with nn = absolute value of the selected output unit). The file
 containing the random number seeds will be called "ran<input file name><run
 number>".

 The error file may contain error messages related to the event generators
 (for instance when the program does not manage to conserve exactly energy or
 another quantity) or to the geometry tracking. Most of those are generally
 only warning messages which can be ignored unless there is a large number of
 them.

 The log file generally contains messages related to fatal errors (input
 errors, overflow, etc.)

 During a multiple run, lines like the following will appear on the user's
 screen:

  ================================ Running FLUKA for cycle # 1 ====================

  Removing links

  Removing temporary files

  Saving output and random number seed

  Saving additional files generated
       Moving fort.47 to /home/fasso/Fluka/test/example01_fort.47
       Moving fort.48 to /home/fasso/Fluka/test/example01_fort.48
       Moving fort.49 to /home/fasso/Fluka/test/example01_fort.49
       Moving fort.50 to /home/fasso/Fluka/test/example01_fort.50
       Moving fort.51 to /home/fasso/Fluka/test/example01_fort.51

  ================================ Running FLUKA for cyle # 2 ====================

  Removing links

  Removing temporary files

  Saving output and random number seed

  Saving additional files generated
       Moving fort.47 to /home/fasso/Fluka/test/example002_fort.47
       Moving fort.48 to /home/fasso/Fluka/test/example002_fort.48
       Moving fort.49 to /home/fasso/Fluka/test/example002_fort.49
       Moving fort.50 to /home/fasso/Fluka/test/example002_fort.50
       Moving fort.51 to /home/fasso/Fluka/test/example002_fort.51

  ================================ Running FLUKA for cycle # 3 ===================

  .....

  ================================ Running FLUKA for cycle # 4 ===================

  .....

  ================================ Running FLUKA for cycle # 5 ===================

  Removing links

  Removing temporary files

  Saving output and random number seed

  Saving additional files generated
      Moving fort.47 to /home/fasso/Fluka/test/example005_fort.47
      Moving fort.48 to /home/fasso/Fluka/test/example005_fort.48
      Moving fort.49 to /home/fasso/Fluka/test/example005_fort.49
      Moving fort.50 to /home/fasso/Fluka/test/example005_fort.50
      Moving fort.51 to /home/fasso/Fluka/test/example005_fort.51

  End of FLUKA run

 At this time, in the working directory, the following new files exist:

  example001_fort.47   example002_fort.47   ....   example005_fort.47
  example001_fort.48   example002_fort.48   ....   example005_fort.48
  example001_fort.49   example002_fort.49   ....   example005_fort.49
  example001_fort.50   example002_fort.50   ....   example005_fort.50
  example001_fort.51   example002_fort.51   ....   example005_fort.51
  example001.out       example002.out       ....   example005.out
  example001.err       example002.err       ....   example005.err

 In Chapter 9} the user can find a comprehensive description of the content of
 the FLUKA standard output. For the purpose of this beginner's guide, it can
 just be pointed out that, according to the content of the USRBDX command, the
 files with extension fort.47 contain, in binary form, the boundary crossing
 estimator output for the required pion fluence and current detectors (for
 more details see Chap. 9}). These files must be combined together to produce
 a table of values with their statistical errors which can be easily
 interfaced by the user to some analysis codes and/or graphic visualisation
 tools. Similarly, the files with extension fort.48 and fort.49 will contain
 the tracklength estimator output, and those with extension fort.50 and
 fort.51 the output from USRBIN.

Previous Index Next