MSUGRA scan

Main goal

The macros on this page can be used to scan any part of the mSUGRA phacespace to determine wich part of the phacespace is still currently allowed by both experiment and theory.

Checking one susy point

The macro susygen.py checkes the compatibility of one specific SUSY point to a certain number of individual constraints. The results of these constaints are written to file. susygen.py is called with: susygen.py < m0 > < m12 > < A0 > < tan(beta) > < sign(mu) > < name resultfile >. Masses should be given in GeV.

Under current form 13 numbers are written to the result file, in the following order: < m0 > < m12 > < A0 > < tan(beta) > < sign(mu) > < theory > < mass neutralino > < mass higgs > < LSP > < BR(B->s gamma) > < relic dencity (omega h^2) > < BR(Bs->mu mu) > The masses are given in GeV.

The value for theory is 0 if the susypoint is theoretically allowed and 1 otherwise. This can easily be changed to give different values for different theoretical constraints.

The value for LSP is equal to the particle number (as used by HERWIG) of the lightest superpartner. 450 = neutralino, 429 = stau.

susygen.py

susygen.py consist of for part, with the first part only responsible for optaining the imputparameters and writing the susy coodinates to the result file.

The second part, called PrepareSusyFile, calles IsaSugra 7.75 to calculate the susy mass-spectrum as well as other usefull parameters. Isasugra7.75 is currently available at /project/atlas/users/nicoleru/SUSY/isajet/isasugra.x . Some information must be given to isasugra in the form of an imputfile. This imputfile is automatically constructed from a basic imputfile: ......... Two files are created by isasugra called <filename> and <filename.txt>. <filename.txt> can imidiatly be used as an imputfile for HERWIG while <filename> contains the same information but in a more easily readable form. If the SUSY point being generated is theoretically excluded but files will be empty and an error will be written to a logfile.

The third part of the program checks for theoretical compatibilty by looking at the logfile. At this point is it is easy to implement some code to differentiate between the different theoretical constraint by looking at the formulation of the error in the logfile.