2
########################################################################
4
If you need more information than provided by this file, contact the
5
author: Andreas van Hameren <hamerenREMOVETHIS@ifj.edu.pl>
7
########################################################################
9
To create a source file for CutTools, execute
13
########################################################################
15
To create a static library "libavh_olo.a",
16
set your Fortran compiler in the file "Config", and execute
20
########################################################################
22
To create a dynamic library "libavh_olo.so" with gfortran,
23
set the Fortran compiler in the file "Config" to gfortran, and execute
27
Put the library "libavh_olo.so" where the linker can find it,
28
or add its position to the path, eg. in bash:
30
export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:DirectoryWhereLibraryIs
32
########################################################################
34
To create just a source file, execute
38
########################################################################
40
If you chose create a library, you can link it to your program.
41
You will then have a module "avh_olo" at your disposal, which provides
42
routines described in the file DESCRIPTION.
44
Many compilers require access to a module-file "avh_olo.mod", which is
45
created along with the library, in order to make the module available
46
to your program when it is compiled.
48
An example of use is given in the directory ./example .
50
If you want just a source file, instead of what is described above you
55
You can use this if you want to include the creation of the source file
56
into the build of your program. Have a look at the file "make_cuttools".
58
There are some variables in the file "Config" you can set:
60
FFLAGS: flags for the Fortran compiler
62
DPKIND: sets the kind of all real and complex variables. The
63
value of DPKIND is a piece of Fortran that goes directly
66
QPKIND: if your compiler provides quadruple precision, you can
67
set this variable to the quadruple precision kind.
69
If you want more than 2 intrinsic kinds, you need to add
70
the necessary lines in the files
71
"avh_olo_comb.f90" and "avh_pc_olo.py".
73
KINDMOD: the values of the kinds may be parameters that are provided
74
by a module you can set with KINDMOD. For example
76
KINDMOD = my_kind_module
77
where my_kind_module provides the parameter my_real_kind.
78
Realize that if you set KINDMOD, you have to compile
79
the source file yourself in order to provide the module.
81
DDTYPE: if you want to use OneLOop at double double precision in
82
combination with dd or qd , then you should set this
83
variable to ddfun90 or qdcpp respectively. If not,
84
then DDTYPE should stay empty.
86
QDTYPE: if you want to use OneLOop at quad double precision in
87
combination with qd , then you should set this variable
88
to qdcpp . If not, then QDTYPE should stay empty.
90
MPTYPE: if you want to use OneLOop at arbitrary precision in
91
combination with mpfun90 or arprec , then you should set
92
this variable to the respective value. If not, then MPTYPE
95
DDF90MOD: if you want to create the library in combination with dd ,
96
then you need to set the directory where the modules
97
of dd can be found. This is not necessary if you
98
just want to create the source file. If you want to use qd ,
99
then only the source file can be provided, and you have
100
to build the library yourself.
102
MPF90MOD: if you want to create the library in combination with
103
mpfun90, you need to set the directory where the modules
104
of mpfun90 can be found. This is not necessary if you
105
just want to create the source file. If you want to use
106
arprec, only the source file can be provided, and you have
107
to build the library yourself.
109
TLEVEL: if you don't want to use the module, but the old-style
110
toplevel routines "avh_olo_..." instead, you need to set
113
CPPINTF: if you want to use OneLOop in C++, then you need to set
115
Have a look at the README in the directory example_cpp
117
########################################################################
121
Routines for IR-divergent functions with all internal masses equal zero
122
based on G. Duplancic and B. Nizic,
123
Eur.Phys.J.C20:357-370,2001 (arXiv:hep-ph/0006249)
124
and on Z. Bern, L.J. Dixon and D.A. Kosower,
125
Nucl.Phys.B412,751(1994) (arXiv:hep-ph/9306240)
127
Routines for IR-divergent functions with non-zero internal masses
128
based on R. Keith Ellis and G. Zanderighi,
129
JHEP 0802:002,2008 (arXiv:0712.1851)
130
and on W. Beenakker, H. Kuijf, W.L. van Neerven, J. Smith,
131
Phys.Rev.D40,54(1989)
132
and on W. Beenakker, S. Dittmaier, M. Kramer, B. Plumper, M. Spira,
133
P.M. Zerwas, Nucl.Phys.B653:151-203,2003(arXiv:hep-ph/0211352)
134
and on E.L. Berger, M. Klasen, T.M.P. Tait,
135
Phys.Rev.D62:095014,2000. (arXiv:hep-ph/0005196)
136
and on W. Beenakker and D. Denner, Nucl.Phys.B338,349(1990)
138
Routines for finite 4-point functions with real masses
139
based on A. Denner, U. Nierste, R. Scharf, Nucl.Phys.B367(1991)637-656
141
Routines for finite 3-point functions obtained from these by sending
142
one mass to infinity, and based on the formulas from
143
G. 't Hooft and M.J.G. Veltman, Nucl.Phys.B153:365-401,1979
145
Routines for finite 4-point functions with complex masses
146
based on Dao Thi Nhung and Le Duc Ninh,
147
Comput.Phys.Commun.180:2258-2267,2009,(arXiv:0902.0325)
148
and on G. 't Hooft and M.J.G. Veltman, Nucl.Phys.B153:365-401,1979
150
Routines for 2-point functions
151
based on A. Denner and S. Dittmaier,
152
Nucl.Phys.B734 (2006) 62-115 (hep-ph/0509141)
154
########################################################################