NLO techniques/Standardization/automation

From Wiki Les Houches 09

Revision as of 15:32, 9 April 2010 by Boudjema (Talk | contribs)
Jump to: navigation, search

Discuss on the various NLO techniques, identify if and what exactly can be standardized in these NLO calculations. Discuss on automation.

People signed up for this group:

Fawzi, Peter, Gudrun, Giampiero, Ian, Tanju, David, Rikkart, Nicolas, Laura, Stefano, Stefan, Nikolas, Ruth, Thomas (R), Maria Vittoria, Duc Ninh, Marcus, Sunhao, Isabella, Son, Vittorio, Lorenzo, Daniel, Darren, Simon (B), Achilleas, Carlo

Les Houches accord for a standard interface between leading order Monte-Carlo tools and one-loop programs (OLPs)

A view slides which are related to the discussion on standardization can be found here (June 2009) [[1]] The starting point for a concrete interface was provided by Tanju and Daniel in this Draft (June 2009).

After extensive discussions and exchange of ideas we have formulated this (preliminary) proposal [[2]] for a MC/OLP interface in December 2009. Several groups and individuals have provided input for this document and work on implementations now. First working examples are expected to be documented in the Les Houches proceedings. We will try to collect relevant program fragments on this page which may serve as guidelines and help for users and providers of MCs and OLPs.

Report from CPC on the BLHA

Reviewer #1:

The authors of the manuscript ``A proposal for a standard interface between Monte Carlo tools and one-loop programs propose an interface for the communication between programs for the calculation of one-loop amplitudes (OLP), and programs dealing with anything else necessary in a next-to-leading (NLO) order calculation. Since this communication is bound to be non-trivial, the existence of such a standard interface would be of great help in the development of full NLO Monte Carlo programs.

Except for a few points, the paper is clearly written.


Point A

The first point that may need clarification is related to the proposed MatrixElementSquarType, in case it is not set to CHsummed. In this case, the MC has to perform color and/or helicity summation, and necessarily has to provide color and/or helicity configurations to the OLP. In the discussion about OLP_EvalSubProcess, it is suggested that the OLP can provide more color and helicity information, but is not mentioned whether the OLP could take such information as input. Only momentum configurations are mentioned as input.

Suggestions for Point A

Suggestions and comments from 
Suggestions and comments from

Point B

Secondly, the paper propagates, eg. at the beginning of page 9, the philosophy for the OLP to provide un-subtracted information, and not only subtracted information. This seems to conflict with the last paragraph of page 15, where it is mentioned that The OLP directly subtracts the collinear and soft divergences.... This probably has to do with the discussed mass regularization, and could be clarified more.

Suggestions for Point B

Suggestions and comments from 
Suggestions and comments from

Then there are a few details: 1. Page 4 after formula 2.7 identifies should be identified

2. Same page, same paragraph the sentence In actual calculations, subtraction methods are applied... maybe should be rephrased, stating that the proposed standard assumes the use of subtraction methods.

3. Among the publications cited in the context of automated evaluation of one-loop amplitudes, it might be appropriate to also mention Automated one-loop calculations: A Proof of concept. A. van Hameren, C.G. Papadopoulos, R. Pittau, JHEP 0909:106,2009.

Personal tools