Changes between Version 1 and Version 2 of Models/USERMOD


Ignore:
Timestamp:
Apr 23, 2014, 1:48:26 AM (10 years ago)
Author:
Olivier Mattelaer
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • Models/USERMOD

    v1 v2  
    1515from this file.
    1616 1. All zero/one value are fixed in the model and can't be changed anymore
    17  2. If a Block has two identical value. Those two value are merged to a single one
     17 2. If a Block has two identical value. Those two value are merged to a single one (but for the width specification)
    1818 3. All couplings which are zero for this param_card are removed from the model.
     19 4. Two value are "special": 9.999999e-1 and 1e-99. Those allow to apply the restriction of the zero coupling but still allowing to modify the associate parameter.
     20 
    1921
    2022To load this restricted model in mg5. you have to do:
    … …  
    2325if XXXX is default, then the import import model MODELNAME load automatically the restriction restrict_default.dat. The original model can then be retrieve by the command import model MODELNAME-full.
    2426
     27Any generation using a restriction model have his own default param_card, corresponding to the card use for the restriction (minus the parameter whcih can not be changed anymore). if a file "default_XXX.dat" exists then this file will be the default param_card for the XXX restricted model.
     28
     29Since 2.1.0, it is possible to define a default param_card which is NO
    2530
    2631== ADD MODEL
    2732
    2833=== STATUS:
    29 Not yet in any official release (current one is 2.0.0)
    30 available at: lp:~maddevelopers/madgraph5/plugin_model
     34PART OF THE OFFICIAL RELEASE (since 2.1.1)
    3135
    3236=== SYNTAX:
    … …  
    3539=== WHAT IT DOES:
    3640- It create a new model named: NAME1__NAME2 (where NAME1 is the name of the current loaded model and NAME2 is the plugin one).
    37 - The new model contains the SUM of all interactions of both model! The code didn't check if the same interactions appears in
    38 both model. If this happens, the new model will contain TWO times the same interactions (and is then likely to be wrong).
     41- The new model contains the union of all interactions of both model! If an interaction exists on both model, it is in principle removed correctly. But we advise to check carefully this point.
    3942- if the options "--recreate" is present and a model NAME1_NAME2 already exists then the code remove that model.
    4043- if the options "--recreate" is NOT present and a model NAME1_NAME2 already exists then code just import NAME1__NAME2 model.
    … …  
    4548
    46491) ALL external parameter which correspond to the same block/id are expected to be identical between the two model.
    47 Be carefull if you use this with some "frblock" since they are likely to have different physical meaning betwen different model.
     50Be careful if you use this with some "frblock" since they are likely to have different physical meaning betwen different model.
    4851
    49522) ALL particles are identified by their PDG_CODE. If a particles of the plugin model has a pdg_code of one particle of the original model
    … …  
    55584) The coupling order takes the minimal value of the coupling order found in both model. This might not be what you want => Probably need to modify
    5659that file manually!
     60
     615) model restriction (see above) of the original model will be propagate to the merged model. No model restriction of the added model will be taken into account.
     62