Difference between revisions of "Generating AtlFast SUSY Events"
| (3 intermediate revisions by the same user not shown) | |||
| Line 5: | Line 5: | ||
='''How to use it'''= | ='''How to use it'''= | ||
| − | Once release 13.0.40 is set on your computer, generating events is really easy. Just copy susymap.py, susygen.py and susyatlfast.py to your own directory. The only thing you need to change before usage is in susyatlfast.py in function DataTransfer() where the directory where the final aods and log file are placed is defined. If you want all data to remain in the directory you are currently working in, you can also simply turn of the DataTransfer() function. | + | Once release 13.0.40 is set on your computer, generating events is really easy. Just copy susymap.py, susygen.py and susyatlfast.py to your own directory. They are located in /project/atals/users/nicoleru/Store/. The only thing you need to change before usage is in susyatlfast.py in function DataTransfer() where the directory where the final aods and log file are placed is defined. If you want all data to remain in the directory you are currently working in, you can also simply turn of the DataTransfer() function. |
Once this path is set, you will only need to work within susymap.py. Here a grid is defined in the 5D mSUGRA phasespace and for each point on that grid events will be generated. Apart from the grid you will have to indicate the top mass as well as the number of events you want generated per point. | Once this path is set, you will only need to work within susymap.py. Here a grid is defined in the 5D mSUGRA phasespace and for each point on that grid events will be generated. Apart from the grid you will have to indicate the top mass as well as the number of events you want generated per point. | ||
| + | |||
| + | To run the macros just type: susymap.py | ||
='''Output'''= | ='''Output'''= | ||
| Line 17: | Line 19: | ||
='''Extra possibilities'''= | ='''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- | + | 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-spectrum, decay modes and some additional information (see *[[Tools_to_scan_the_mSUGRA_phasespace | Tools to scan the mSUGRA phasespace ]]) is available from 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. |
| + | |||
| + | The created aods can be read by AMA. A default config file to read these aods is located at: /project/atlas/users/nicoleru/Store/ConfigAODAtlfast.conf | ||
Latest revision as of 08:46, 18 April 2008
STILL UNDER CONSTRUCTION
This page shows how to automatically generate events for any number of different points in the mSUGRA phasespace, using the macro's introduced in * Tools to scan the mSUGRA phasespace and an additional macro called susyatlfast.py. It is assumed that the release 13 environment is properly set on the machine you are using. To see how this is achieved 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 your computer, generating events is really easy. Just copy susymap.py, susygen.py and susyatlfast.py to your own directory. They are located in /project/atals/users/nicoleru/Store/. The only thing you need to change before usage is in susyatlfast.py in function DataTransfer() where the directory where the final aods and log file are placed is defined. If you want all data to remain in the directory you are currently working in, you can also simply turn of the DataTransfer() function.
Once this path is set, you will only need to work within susymap.py. Here a grid is defined in the 5D mSUGRA phasespace and for each point on that grid events will be generated. Apart from the grid you will have to indicate the top mass as well as the number of events you want generated per point.
To run the macros just type: susymap.py
Output
After the program is run you should have one directory made per susypoint, containing an aod as well as a log file. This log file contains all output information of Herwig and AtlFast, which contains information like the cross-section and is important to check whether no problems occurred.
Also an output file is written in your work directory which contains some general 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-spectrum, decay modes and some additional information (see * Tools to scan the mSUGRA phasespace ) is available from 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.
The created aods can be read by AMA. A default config file to read these aods is located at: /project/atlas/users/nicoleru/Store/ConfigAODAtlfast.conf