REVIEW 1 cited by
Hardware acceleration for next-to-leading order event generation within MadGraph5_aMC@NLO
Not yet reviewed by Pith; the record is open.
This paper has not been read by Pith yet. Machine review is queued; the pith claim, tier, and objections will appear here once it completes.
SPECIMEN: schema-true, not a live event
T0 review · schema-true
One-sentence machine reading of the paper's core claim.
pith:XXXXXXXX · record.json · timestamp
read the original abstract
As the quality of experimental measurements increases, so does the need for Monte Carlo-generated simulated events - both with respect to the total amount and to their precision. In perturbative methods, this involves the evaluation of higher order corrections to the leading order (LO) scattering amplitudes, including real emissions and loop corrections. Although experimental uncertainties today are larger than those of simulations, at the High Luminosity LHC experimental precision is expected to be above the theoretical one for events generated below next-to-leading order (NLO) precision. As forecasted hardware resources will not meet CPU requirements for these simulation needs, speeding up NLO event generation is a necessity. In recent years, collaborators across Europe and the United States have been working on CPU vectorisation of LO event generation within the MadGraph5_aMC@NLO framework, as well as porting it to GPUs, to major success. Recently, development has also started on vectorising NLO event generation. Due to the more complicated nature of NLO amplitudes this development faces several difficulties not accounted for in the LO development, but it shows promise. Here, we present these issues as well as the current status of our event-parallel NLO implementation.
Forward citations
Cited by 1 Pith paper
-
Data-parallel leading-order event generation in MadGraph5_aMC@NLO
CUDACPP gives MadGraph data-parallel helicity amplitudes, delivering linear SIMD CPU speed-ups and up to order-of-magnitude GPU speed-ups for high-multiplicity QCD event generation.
Discussion (0). Sign in to comment.