Installation of
Micromegas_5.2 (Freeze-in and Freeze-out) |
The compressed File micromegas_5.2.4.tgz is about 13Mb. DOWNLOAD
micromegas_5.2.4 was tested for Linux and Darwin.
First unpack the file, for example tar -zxvf micromegas_5.2.4.tgz
This will create a directory called micromegas_5.2.4
I.
General Installation
In this directory you should first launch,
gmake
(If you do not have 'gmake' use
'make' instead)
The command gmake should generate files with compilers flags
and compile
CalcHEP_src/bin/s_calchep
sources/micromegas.a
Possible problems are discussed in Section VI below.
II. The MSSM (for
a general description of all the features go here)
To work with the MSSM go to the MSSM directory.
To generate the executable use
gmake main=<source file>
where <source file> is either a C or Fortran file, for example
main.c or main.F
To launch the excutable main.c
./main input
Where input is either a set of input parameters
r the name of a data file (for example mssm1.par) according to the option
chosen in main.c. In both cases instructions are given on the screen. The list of functions you can use in your
programs is described in arXiv:1305.0237 [hep-ph]
III. Models
One model with two-component dark matter and six models with only one dark matter candidate are provided by the micrOMEGAs team for a seamless
integration within micrOMEGAs 4.3:
To generate the executable and launch the
program, move to the appropriate directory and
gmake main=main.c
./main data1.par
(or any other input data file)
Other models are also available and can be downloaded
The CalcHEP_src/FlagsForMake and CalcHEP_src/FlagsForSh
contain options for compilation and should contain identical settings in
different formats. These files initiated by the getFlags command launched from
the CalcHEP_src directory.
If FlagsForSh does not exist, getFlags creates it according to the operation
system name returned by the 'uname' Unix command.
If FlagsForSh exists, getFlags reads all parameters from this file,
checks and modifies them if it needs, and writes down new FlagsForSh and
FlagsForMake. It also informs you in case of problem.
In case of problem the user can change compiler flags
written in FlagsForSh and launch getFlags again until FlagsForMake
is generated without any error code. The meaning of all flags is explained in
the FlagsForSh file. For example you might have to change the name of the
Fortran compiler (set by default to g77).