Changes between Initial Version and Version 1 of MadSpin

02/16/14 02:38:03 (6 years ago)



  • MadSpin

    v1 v1  
     1= MadSpin =
     3== References ==
     5   Code/Manual:
     6      Automatic spin-entangled decays of heavy resonances in Monte Carlo simulations[[BR]]
     7      Pierre Artoisenet, Rikkert Frederix, Olivier Mattelaer, Robbert Rietkerk[[BR]]
     10   Code based on the following method:
     11      Angular correlations of lepton pairs from vector boson and top quark decays in Monte Carlo simulations[[BR]]
     12      Stefano Frixione, Eric Laenen, Patrick Motylinski, Brian R. Webber[[BR]]
     15=== How to run MadSpin in standalone===
     17   In standalone, one launches a MadSpin session by typing:
     18   {{{
     19   ./MadSpin/madspin
     20   }}}
     21   This opens a prompt, similar to that of the MadGraph5 Suite. The following commands are then available:
     22      * import FILE:[[BR]]
     23        imports the LO or NLO lhe file and reads the associated header in order to load relevant information, e.g. the relevant model.
     24      * define LABEL = PART1 PART2 ... :[[BR]]
     25        allows to define an additional multi-particle tag. The multi-particle tags defined in the header of the file are automatically recognized.
     26      * decay PROCESS:[[BR]]
     27        specifies the decay branch initiated by an unstable particle to be decayed by MadSpin. Multi-particle tags can be used for the final state particles.
     28      * set OPTION VALUE:[[BR]]
     29        allows to change some internal options of MadSpin such as the seed or the value of the maximal weight in the unweighting procedure. Type “help options” in the interface for more details on the various available options. (and/or see the list below)
     30      * launch:[[BR]]
     31        runs MadSpin according to the specified options/decay channels.
     32      * help COMMAND:[[BR]]
     33        provides detailed information on a specific command.
     35=== How to run MadSpin on the flight ===
     37   MadSpin can also be called directly via the MadEvent/aMC@NLO script
     38   (via the launch command or the ./bin/generate_events script). In this case, the script will
     39   request some information about the programs to run.
     40   For MadEvent the question is:
     41   {{{
     42The following switches determine which programs are run:
     43 1 Run the pythia shower/hadronization:                   pythia=NOT INSTALLED
     44 2 Run PGS as detector simulator:                            pgs=NOT INSTALLED
     45 3 Run Delphes as detector simulator:                    delphes=NOT INSTALLED
     46 4 Decay particles with the MadSpin module:              madspin=ON
     47 5 Add weight to events based on coupling parameters:   reweight=OFF
     48  Either type the switch number (1 to 5) to change its default setting,
     49  or set any switch explicitly (e.g. type 'madspin=ON' at the prompt)
     50  Type '0', 'auto', 'done' or just press enter when you are done.
     51 [0, 4, 5, auto, done, madspin=ON, madspin=OFF, madspin, reweight=ON, ... ][60s to answer]
     52   }}}
     53   While for aMC@NLO she is:
     54   {{{
     55The following switches determine which operations are executed:
     56 1 Perturbative order of the calculation:                              order=NLO
     57 2 Fixed order (no event generation and no MC@[N]LO matching):   fixed_order=OFF
     58 3 Shower the generated events:                                       shower=ON
     59 4 Decay particles with the MadSpin module:                          madspin=ON
     60  Either type the switch number (1 to 4) to change its default setting,
     61  or set any switch explicitly (e.g. type 'order=LO' at the prompt)
     62  Type '0', 'auto', 'done' or just press enter when you are done.
     63 [0, 1, 2, 3, 4, auto, done, order=LO, order=NLO, ... ][60s to answer]
     64    }}}
     65   In both case, if you can ask to run MadSpin on the flight by typing madspin=ON
     67   The program will propose, in a second step, to edit the madspin_card.dat. This file contains the command lines associated with the
     68   MadSpin program that we described in the previous section. Note that MadGraph5 will figure out which event file has to be decayed, so that you do not need to    include the “import” command in this file. After these questions have been answered, MadGraph5 proceeds with the Monte Carlo generation:
     69     1. it generates the LHE event file before decay
     70     2. it executes MadSpin
     71     3. if requested, it submits the decayed events to a shower/hadronisation program.
     73=== Full list of options ===
     75   Note some of the options are not in the "help" mention above seems they are not fully secure. They allow much more flexibility but need to be use with great care.
     77   1. '''import model ModelNane ParamCardPath [--bypass_check]'''[[BR]]
     78      Allows to use another model/param_card than the one used for the generation of the events. By default some check are done that the old/new param_card seems compatible but if the optional argument --bypass_check is included.[[BR]]
     79      New in v2.1.0
     80   1. '''set ms_dir PATH'''[[BR]]
     81      If path doesn't exists, create a directory with all the information that MadSpin needs to decayed events. This stores:
     82         * The matrix elements
     83         * The maximal weights
     84         * The status of the seed (can be changed via the card)
     85      If path exists, use the information present in that directory which allows to bypass the initialization phase. Note that this is valid only for the SAME param_card. We actually check that this is the case.
     86   1. '''set BW_effect True|False:''' [default:True] [[BR]]
     87      reshuffle the momenta to describe corrrectly the Breit-Wigner of the decayed particle
     88   1. '''set seed VALUE:'''[[BR]]
     89      fix the value of the seed to a given value. By default use the current time to set the seed. random number are generated by the python module random using the Mersenne Twister generator. It has a period of 2**19937-1.
     90   1. '''set max_running_process VALUE''':[[BR]]
     91      allow to limit the number of open file used by the code. The number of running is raising like 2*VALUE