Changes between Initial Version and Version 1 of Models/USERMOD

Timestamp:

Jan 17, 2014, 9:34:03 PM (11 years ago)

Author:

Olivier Mattelaer

Comment:

--

Models/USERMOD

@@ +1 @@
+== RESTRICT MODEL
+
+=== STATUS:
+PART OF THE OFFICIAL RELEASE
+
+=== PROBLEM:
+
+You want to set a mass to ZERO/ REMOVE PART of the model for speed point of view/...
+
+=== SOLUTION:
+ you have to define a file
+restrict_XXXX.dat in the UFO model
+this file should be a valid param_card.dat
+(so you can create this file by doing: python write_param_card.py in the UFO directory, then rename the output file)
+from this file.
+ 1. All zero/one value are fixed in the model and can't be changed anymore
+ 2. If a Block has two identical value. Those two value are merged to a single one
+ 3. All couplings which are zero for this param_card are removed from the model.
+
+To load this restricted model in mg5. you have to do:
+import model MODELNAME-XXXX
+
+if 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.
+
+
+== ADD MODEL
+
+=== STATUS:
+Not yet in any official release (current one is 2.0.0)
+available at: lp:~maddevelopers/madgraph5/plugin_model
+
+=== SYNTAX:
+ADD MODEL NAME [--recreate] [--output=XXX]
+
+=== WHAT IT DOES:
+- It create a new model named: NAME1__NAME2 (where NAME1 is the name of the current loaded model and NAME2 is the plugin one).
+- The new model contains the SUM of all interactions of both model! The code didn't check if the same interactions appears in 
+both model. If this happens, the new model will contain TWO times the same interactions (and is then likely to be wrong). 
+- if the options "--recreate" is present and a model NAME1_NAME2 already exists then the code remove that model.
+- if the options "--recreate" is NOT present and a model NAME1_NAME2 already exists then code just import NAME1__NAME2 model.
+- The options output allows to specify the name of the resulting model (can then be imported via "import model XXX") 
+
+
+=== MORE DETAILS
+
+1) ALL external parameter which correspond to the same block/id are expected to be identical between the two model. 
+Be carefull if you use this with some "frblock" since they are likely to have different physical meaning betwen different model.
+
+2) 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
+then we assume the two particles to be identical and to have the same mass/same width. IF one of the two model has that particle defined with
+a ZERO mass and not the other, the resulting mass will ALWAYS be the non zero one.
+
+3) If two parameters have the same name for different physical quantity, then the plugin variable will be renamed automatically.
+
+4) 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
+that file manually!