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. Currently the value 0 is written to the resultfile if the no error is found, and the program continues on to the forth and final part. If the susy point is theoretically excluded the value 0 is written to file, and the program is finished.

The forth part of the macro is gets the necessary values from either <filename> or <filename.txt> and are then written to the resultfile. At this point it is easiy to add any other values dirrectly optained from either the susy particle masses or any other information given by isasugra.

first time useage

To use this macro it is probably easiest to copy both susygen.py and .... to your own dirrectary. Furthermore you directory path (dir_own) should be changed (Line ...) as well as the path to where <filename> and <filename.txt> should be created (Line...).

running over a grid in the mSUGRA phacespace

To only check one specific susy point it is a lot easier to simply run isasugra manualy and check the vales dirrectly form <filename> then to run the susygen.py macro. However the macro becaumes usefull when a large amount of points need to be checked. This can be done using the susymap.py macro. This is a very simple program that just diffines a grid in the 5D susy phacespace and calles susygen.py for every point on that grid.

The initial and final value of the phasespace of interest for each parameter must be specified as well as the number of steps for each parameter. The name for the resultfile must also be given and results for every point will be written to the same file.

It is important to note that the name for intermidiate files used by susygen.py dipend on the susy coordinates and therefore all these files will remain. The exeption to this is the logfile containing the possible error due to theoretical compatibility, which will be overwritten for each point. If you want to save those file, the logfilename in susygen.py should be made coordinates dipendent.