Changes between Version 4 and Version 5 of DevelopmentPage/BeyondProjects

Timestamp:

Mar 2, 2010, 3:08:26 PM (14 years ago)

Author:

Olivier Mattelaer

Comment:

--

DevelopmentPage/BeyondProjects

@@ -12 +12 @@
  * Will/Priscila : Python Module (!HelasProduction) to take the info in model.py and produce the corresponding HELAS library.
  * Will/Michel : Integration of !HelasProduction into MG5 with possible selection of the relevant subroutines in a given process
+
+== Python Strategy ==
+
+This will define a full strategy for the HelasRoutine.
+
+   * Feynrules should output a dictionary indicating which vertex uses which (set) of HelasRoutine
+   * a Python-Helas Routine should looks like as
+       
+       obj = Gamma(('i'),('j','k')) * P(('i'),('l') * P(('m'),('n') + Gamma(('i'),('j','k')) * Sigma(('i','m'))
+       #High Level structure
+
+   * then we should be able to combine those structure
+       obj3 = obj1 * obj2
+       obj3.simplify()
+   * we should be able to write code in a file
+       low_level_object = obj3.expand() # use a specific representation of the representation 
+       low_level_object.write_in_XXXX(output_file)
+       
+
+So We Need different Class Object
+   
+   * A LorentzObject: basic High-Level object (everything shoud derive from it). All children (Gamma,P, ...) should define multiplication/simplification between High-Level object and a representation (in the spin basis)
+   
+   * Variable for the concrete representation of High-Level Object, we will need an object describing (complex) variable. When this will be expanded we will need to have defined the Sum (AddVariable) and the multiplication of variable (MultVariable). Those variable should then be associate to a file description in the relevant output format.
+
+   * The second basic object should be a low level variable in order to represent the basic rules extracted from the concrete representation of the HelasRoutine. 
+
+
+ 
+       
+
+ 
+
+
+
+