Reggeon field theory for large Pomeron loops

Tolga Altinoluk, Alex Kovner, Eugene Levin, Michael Lublinsky

Research output: Contribution to journalArticlepeer-review

27 Scopus citations


We analyze the range of applicability of the high energy Reggeon Field Theory H RFT derived in [1]. We show that this theory is valid as long as at any intermediate value of rapidity η throughout the evolution at least one of the colliding objects is dilute. Importantly, at some values of η the dilute object could be the projectile, while at others it could be the target, so that H RFT does not reduce to either H JIMWLK or H KLWMIJ . When both objects are dense, corrections to the evolution not accounted for in [1] become important. The same limitation applies to other approaches to high energy evolution available today, such as for example [2, 3] and [4-6]. We also show that, in its regime of applicability H RFT can be simplified. We derive the simpler version of H RFT and in the large N c limit rewrite it in terms of the Reggeon creation and annihilation operators. The resulting H RFT is explicitly self dual and provides the generalization of the Pomeron calculus developed in [4-6] by including higher Reggeons in the evolution. It is applicable for description of 'large' Pomeron loops, namely Reggeon graphs where all the splittings occur close in rapidity to one dilute object (projectile), while all the merging close to the other one (target). Additionally we derive, in the same regime expressions for single and double inclusive gluon production (where the gluons are not separated by a large rapidity interval) in terms of the Reggeon degrees of freedom.

Original languageEnglish
Article number75
JournalJournal of High Energy Physics
Issue number4
StatePublished - Apr 2014


FundersFunder number
Seventh Framework Programme256313, 279579, 318921


    • Deep Inelastic Scattering
    • QCD
    • Resummation


    Dive into the research topics of 'Reggeon field theory for large Pomeron loops'. Together they form a unique fingerprint.

    Cite this