NMSSMTOOLS


NMSSMTools

NMSSMTools contains NMHDECAY, NMSPEC, NMGMSB, NMHDECAY_CPV, NMSDECAY, micrOMEGAs and SmodelS.

Authors: Ulrich Ellwanger*, Cyril Hugonie**

* Laboratoire de Physique Theorique, Universite de Paris-Sud and Univ. Paris-Saclay, F-91405 Orsay, France.
** Laboratoire Univers et Particules de Montpellier, Universite de Montpellier, F-34095 Montpellier, France.

 


How to use NMSSMTools

After the download of NMSSMTools_x.tgz (where x is the version number), type "tar zxvf NMSSMTools_x.tgz". This will create a directory named NMSSMTools_x. Go into this directory. There you find the script file "run" and the directories "sources", "main", "micromegas" and "smodels", which contain source files; "EXPCON", which contains data files corresponding to experimental constraints; "SAMPLES", which contains sample input and output files.

Compilation

To compile, type first "make init", then "make". A first compilation may take a while, since many subroutines of micrOMEGAs and SmodelS are compiled. Executable routines are created in the directory "main". If a subroutine in the directory "sources" is modified, one has to type "make init" and "make" again. If a routine in the directory "main" is modified, it suffices to type "make" again. To delete all the already compiled codes type "make clean".

Input files

From the version 2.0.0 onwards, the task to be performed by an input file is independent from its name. Any name is allowed, provided it contains the three letters "inp"; it can be of the general form PREFIXinpSUFFIX where PREFIX and SUFFIX can contain dots etc..

The input file can be located in any directory specified by a PATH.

To run any input file PREFIXinpSUFFIX, type "run PATH/PREFIXinpSUFFIX". (PATH is optional; if absent, the input file has to be located in the same directory as the script file "run".)

The output files are located in the directory specified by PATH. They have the following format:

However, the task to be performed by an input file must be specified in the BLOCK MODSEL at the beginning (see the SLHA2 conventions in [1]).

For more details see the description in README.

 


REFERENCES