Difference between revisions of "Generating AtlFast SUSY Events"
Line 1: | Line 1: | ||
'''STILL UNDER CONSTRUCTION''' | '''STILL UNDER CONSTRUCTION''' | ||
− | This page shows how to auatomatically generate events for any number of different | + | This page shows how to auatomatically generate events for any number of different points in the mSUGRA phace-space, using the macro's introduced in *[[Tools_to_scan_the_mSUGRA_phasespace | Tools to scan the mSUGRA phasespace ]] and an aditional macro called susyatlfast.py. It is assumed that the release 13 enviorment is proparly set on the machine you are using. To see how this is atchieved look at: *[[Setting_up_13.0.30 at Nikhef | Setting up Athena 13.0.30 with slc3 and slc4 at Nikhef]]. |
+ | |||
+ | ='''How to use it'''= | ||
+ | |||
+ | Once release 13.0.40 is set on you computer, genarating events is realy easy. Just copy susymap.py, susygen.py and susyatlfast.py to your own directory. The only thing you need to change before useage is in susyatlfast.py in function DataTrensfer() where the directory where the final aods and log file are placed is difined. If you want all data to remain in the directory you are curently working in, you can also simply turn of the DataTransfer() function. | ||
+ | |||
+ | Once this path is set, you will only need to work withing susymap.py. Here a grid is difined in the 5D mSUGRA phasespace and for each point on that grid events will be genrated. Appart from the grid you will have to indicte the top mass as well as the number of events you want generated per point. | ||
+ | |||
+ | ='''Output'''= | ||
+ | |||
+ | After the program is run you should have one directory made per susypoint, containg an aod as well as a log file. This logfile contains all output information of Herwig and AtlFast, which is important to check whether npo problems aucured and which contains information like the corss-section. | ||
+ | |||
+ | Also an output file is written in your work directory which contains some genral information on each susy point. For more information on this look at: *[[Tools_to_scan_the_mSUGRA_phasespace | Tools to scan the mSUGRA phasespace ]]. | ||
+ | |||
+ | ='''Extra possibilities'''= | ||
+ | |||
+ | susygen.py contains a function called DetermineEventGeneration() which is there to check whether events should be generated. The default function only checks whether the number of events that you want generated is no equal to 0. However considering all information about the susy mass-sepectrum, decay modes and some additional information (see *[[Tools_to_scan_the_mSUGRA_phasespace | Tools to scan the mSUGRA phasespace ]]) is available form IsaSugra, it is possible to include other restrictions like: only generate events if the Higgs-mass is above 114 GeV, or if the neutralino is the LSP. |
Revision as of 14:42, 17 April 2008
STILL UNDER CONSTRUCTION
This page shows how to auatomatically generate events for any number of different points in the mSUGRA phace-space, using the macro's introduced in * Tools to scan the mSUGRA phasespace and an aditional macro called susyatlfast.py. It is assumed that the release 13 enviorment is proparly set on the machine you are using. To see how this is atchieved look at: * Setting up Athena 13.0.30 with slc3 and slc4 at Nikhef.
How to use it
Once release 13.0.40 is set on you computer, genarating events is realy easy. Just copy susymap.py, susygen.py and susyatlfast.py to your own directory. The only thing you need to change before useage is in susyatlfast.py in function DataTrensfer() where the directory where the final aods and log file are placed is difined. If you want all data to remain in the directory you are curently working in, you can also simply turn of the DataTransfer() function.
Once this path is set, you will only need to work withing susymap.py. Here a grid is difined in the 5D mSUGRA phasespace and for each point on that grid events will be genrated. Appart from the grid you will have to indicte the top mass as well as the number of events you want generated per point.
Output
After the program is run you should have one directory made per susypoint, containg an aod as well as a log file. This logfile contains all output information of Herwig and AtlFast, which is important to check whether npo problems aucured and which contains information like the corss-section.
Also an output file is written in your work directory which contains some genral information on each susy point. For more information on this look at: * Tools to scan the mSUGRA phasespace .
Extra possibilities
susygen.py contains a function called DetermineEventGeneration() which is there to check whether events should be generated. The default function only checks whether the number of events that you want generated is no equal to 0. However considering all information about the susy mass-sepectrum, decay modes and some additional information (see * Tools to scan the mSUGRA phasespace ) is available form IsaSugra, it is possible to include other restrictions like: only generate events if the Higgs-mass is above 114 GeV, or if the neutralino is the LSP.