TWINPHOX version 1.0

Twinphox has been tested on DEC Alpha and Linux PC/Laptop.
Before running the program, the user is advised to read the warnings concerning the limitations of applicability of the code.

Structure of the program

working src pdfs pawres read_ntuple basesv5.1
Directory which contains the files: "Makefile", "parameter.indat", "param_histo.indat" and "" Directories containing all the source files Directory containing the photon pdfs afg and afg02 Directory where the histograms will be stored Directory where the ntuple can be stored Directory containing the BASES/SPRING package


  1. Load the TWINPHOX code as gzipped .tar file and unpack it.
  2. In the directory "working", there is a Makefile (using the GNU makefile).
    1. The user has to verify that the fortran compiler called in the Makefile is the one implemented on his machine.
      The default is the f77 DEC fortran compiler FC = f77. On Linux PCs use the GNU compiler g77.
    2. Options of compilation:
      FFLAGS = -O : the compilation flag FFLAGS = -O corresponds to the default level of optimization used by the f77 DEC
      compiler (it works also with g77). For any alternative choice of optimization, please see your compiler's manual.
    3. The user has to verify that the choice of the makefile to build the BASES library is the one corresponding to his machine.
      One can choose between:
      Makefile.dec, Makefile.f2c, Makefile.hiux, Makefile.hpux, Makefile.sgi, Makefile.sun, Makefile.tpl, Makefile.linux
      depending on the computer to be used. The default is
      MAKEBASES = Makefile.dec
    4. The program uses the exe cernlib which is not provided with the program package because it is very likely that the cernlib
      is already installed on your system (if not you can get it from the CERN program library ).
      The user has to verify that the path to the CERN library on his system has been set correctly.
      Default: PATHCERNLIB = cern/pro/bin

  3. Run once the Makefile with the option bases ("gmake bases") to create the library for Bases/Spring.

To run the program

  1. Fix the input parameters of your choice in the file "parameter.indat" in the directory "working".
    This is the main input file containing the parameters for integration and event generation.
    Further information on these parameters is given directly in this file.
    If you also would like to project events into histograms, define the corresponding parameters in the file "param_histo.indat".
  2. To run the perl script "" which creates the executable files, type "perl". This does the following:
    1. The two files "parameter.indat" and "param_histo.indat" containing the input parameters are read automatically.
      In case you have several parameter files with different names, you simply have to specify the names of your parameter files as options: type
      "perl --parameter your_parameterfilename --histo your_param_histofilename".
      Note that "param_histo.indat" will be read only if the flag "histo" in the file "parameter.indat" has been selected.
    2. automatically rewrites the Makefile according to the options you chose in "parameter.indat", and runs the compiler.
    3. creates an executable file called "run_string.exe" where "string" is the name of the run defined in "parameter.indat". You have to execute this file with your favorite options.
    4. creates a directory called "resultstring".
      In this directory, there will be a file "histoNameHisto.outdat" containing a summary of the input which "" has read from "param_histo.indat". The string NameHisto used to label the files containing the histograms (or the ntuple) is defined in "parameter.indat".
      The directory "resultstring" also will contain subdirectories called
      "dddstring" and/or
      depending on which subprocesses you selected in your input. The shorthand "ddd" stands for the contribution where both the initial state and the final state photons are direct. (Note that the final state photon is always direct when using Frixione's isolation criterium, since the fragmentation part does not contribute.) In "drd" the initial state photon travelling in positive z-direction is direct and the other one is resolved, in "rdd" the reverse is true. In "rrd" both photons are resolved. So the structure of the output is the following:

      histoNameHisto.outdat dddstring drdstring rddstring rrdstring
      parameters read from "param_histo.indat" output files specified below see below see below see below
      "output.param" parameters read from parameter.indat
      "sigmaint.res" physical integrated cross-section
      "integral.res" results of integration of absolute values of pseudo-cross sections;
      no physical meaning, needed for normalization of generated events
      "*.bs" results of the grid for each pseudo-cross section; needed for event generation
      "twinphox.log" details of the integration by BASES (efficiency, convergence behaviour, accuracy,time per point, ...)


Back to main page

Back to Twinphox presentation page