Changes between Version 1 and Version 2 of FAQ-NewPhysics-1


Ignore:
Timestamp:
04/06/12 16:33:02 (8 years ago)
Author:
trac
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • FAQ-NewPhysics-1

    v1 v2  
    33== How can I implement a new physics model in Software.MadGraph / Software.MadEvent ? ==
    44
    5 === The "old" way : using {{{USRMOD}}} v1 ===
    6 This is "traditional" way to create a new physics model in Software.MadGraph / Software.MadEvent v4. You should use the {{{USRMOD}}} template directory present in the {{{Models}}} directory. The full procedure to follow is extensively described [http://cp3wks05.fynu.ucl.ac.be/Manual/usrmod.html here].
     5=== The "old" way : using {{{
     6USRMOD
     7}}} v1 ===
     8This is "traditional" way to create a new physics model in Software.MadGraph / Software.MadEvent v4. You should use the {{{
     9USRMOD
     10}}} template directory present in the {{{
     11Models
     12}}} directory. The full procedure to follow is extensively described [http://cp3wks05.fynu.ucl.ac.be/Manual/usrmod.html here].
    713
    814This method has been successfully used over the past to create several new Physics models. However, it presents two important disadvantages:
    915   * The base model is always the SM and the possible modifications are restricted (e.g. removing a particle is not possible). This was due to the important structural differences in the original BSM models provided with Software.MadGraph / Software.MadEvent v4.
    1016   * Feynman rules should be computed by hand.
    11 To address these issues, two new methods are now available and should be preferentially used (starting from the future version 4.6, old models files, including those produced with the {{{USRMOD}}} v1, will only be passively supported).
     17To address these issues, two new methods are now available and should be preferentially used (starting from the future version 4.6, old models files, including those produced with the {{{
     18USRMOD
     19}}} v1, will only be passively supported).
    1220
    13 === The "new" way : using [http://feynrules.phys.ucl.ac.be FeynRules] and/or {{{USRMOD}}} v2 ===
     21=== The "new" way : using [http://feynrules.phys.ucl.ac.be FeynRules] and/or {{{
     22USRMOD
     23}}} v2 ===
    1424
    1525==== [http://feynrules.phys.ucl.ac.be FeynRules] ====
     
    2030Thanks to its high capabilities, including a user friendly interface, the automatized model generation for arbitrary QFT physics theories and robust validation procedures, [http://feynrules.phys.ucl.ac.be FeynRules] and the corresponding interface will be the default tool to generate important Software.MadGraph / Software.MadEvent models starting from version 4.6.
    2131
    22 ==== {{{USRMOD}}} v2 ====
    23 In order to keep the {{{USRMOD}}} approach flexibility with the new models produced by the [http://feynrules.phys.ucl.ac.be FeynRules] package, a new independent version of the {{{USRMOD}}} scripts, called {{{USRMOD}}} v2, has been released. The "philosophy" remains the same, i.e. starting from a base model, the user add/remove/modify particles, interactions and/or parameters, then run the script and finally edit the relevant coupling expressions.
     32==== {{{
     33USRMOD
     34}}} v2 ====
     35In order to keep the {{{
     36USRMOD
     37}}} approach flexibility with the new models produced by the [http://feynrules.phys.ucl.ac.be FeynRules] package, a new independent version of the {{{
     38USRMOD
     39}}} scripts, called {{{
     40USRMOD
     41}}} v2, has been released. The "philosophy" remains the same, i.e. starting from a base model, the user add/remove/modify particles, interactions and/or parameters, then run the script and finally edit the relevant coupling expressions.
    2442
    2543Compare to the first version, it has the following advantages:
    26    * Fully compatible with (and ''only'' with) all models produced by [http://feynrules.phys.ucl.ac.be FeynRules], so the base model can be the SM but also any other model previously produced, including those produced by the {{{USRMOD}}} v2 itself!
    27    * No limitation for the possible modifications. The {{{USRMOD}}} v2 propose to first save a "copy" of the base model and adjust all files to reflects the user changes.
     44   * Fully compatible with (and ''only'' with) all models produced by [http://feynrules.phys.ucl.ac.be FeynRules], so the base model can be the SM but also any other model previously produced, including those produced by the {{{
     45USRMOD
     46}}} v2 itself!
     47   * No limitation for the possible modifications. The {{{
     48USRMOD
     49}}} v2 propose to first save a "copy" of the base model and adjust all files to reflects the user changes.
    2850   * Safer thanks to additional internal consistency checks
    2951   * Evolutive object-oriented Python code
     
    3860
    3961
     62