Draft

From Wiki Les Houches 09

(Difference between revisions)
Jump to: navigation, search
(Implementation proposal)
(Initialisation phase)
Line 24: Line 24:
= Implementation proposal =
= Implementation proposal =
-
= Initialisation phase =
+
== Initialisation phase ==
 +
 
 +
In this phase the MCP asks the OLE for a subprocess.
 +
 
 +
 
 +
 
 +
A list of subprocesses might be loaded using another function call. Every line of this file will correspond to the argument of a singe call to NewSubprocess

Revision as of 17:03, 12 June 2009

This is a working draft for an interface between one-loop amplitude programs and monte carlo programs.


Contents

Goal of the interface

The goal of the interface is to facilitate the transfer of information between one-loop programs (which we will call one-loop provider OLP or one-loop engine depending on whether we mean the method/work (Golem, Rocket, Helac one-loop, BlackHat, ...) or the actual run time entity) which provide one-loop matrix element and the program the does the integration over the phasespace (which we will call MC).

Model of the interaction between MC and OLE

The model of the interaction between the MC and OLE assumes two phases which we will call "initialization" and "run time".


1. Initialization

During this phase the MC sets up the OLE. This means setting up the parameters and fixing options that are offered by the OLP

  • masses, width
  • operating mode, for example which approximation (leading color, massless b's, ...)
  • schemes (renormalization, factorization)

2. Run time

During this phase the MCP queries the OLE for the value of a virtual matrix element.

Implementation proposal

Initialisation phase

In this phase the MCP asks the OLE for a subprocess.


A list of subprocesses might be loaded using another function call. Every line of this file will correspond to the argument of a singe call to NewSubprocess

Personal tools