Journal article
Pinning down the large-x gluon with NNLO top-quark pair differential distributions
- Abstract:
- Top-quark pair production at the LHC is directly sensitive to the gluon PDF at large x. While total cross-section data is already included in several PDF determinations, differential distributions are not, because the corresponding NNLO calculations have become available only recently. In this work we study the impact on the large-x gluon of top-quark pair differential distributions measured by ATLAS and CMS at √ s = 8 TeV. Our analysis, performed in the NNPDF3.0 framework at NNLO accuracy, allows us to identify the optimal combination of LHC top-quark pair measurements that maximize the constraints on the gluon, as well as to assess the compatibility between ATLAS and CMS data. We find that differential distributions from topquark pair production provide significant constraints on the large-x gluon, comparable to those obtained from inclusive jet production data, and thus should become an important ingredient for the next generation of global PDF fits.
- Publication status:
- Published
- Peer review status:
- Peer reviewed
Actions
Access Document
- Files:
-
-
(Preview, Version of record, pdf, 1.3MB, Terms of use)
-
- Publisher copy:
- 10.1007/JHEP04(2017)044
Authors
+ Science and Technology Facilities Council
More from this funder
- Grant:
- ST/L002760/1
- ST/K004883/1
- ST/M003787/1
- Publisher:
- Springer Verlag
- Journal:
- Journal of High Energy Physics More from this journal
- Volume:
- 2017
- Issue:
- 44
- Publication date:
- 2017-04-10
- Acceptance date:
- 2017-03-27
- DOI:
- EISSN:
-
1029-8479
- Keywords:
- Pubs id:
-
pubs:687525
- UUID:
-
uuid:d623771f-34ac-4711-b3bf-8105787eca94
- Local pid:
-
pubs:687525
- Source identifiers:
-
687525
- Deposit date:
-
2017-03-30
- ARK identifier:
Terms of use
- Copyright date:
- 2017
- Notes:
- © The Author(s) 2017. JHEP is an open-access journal funded by SCOAP3 and licensed under CC BY 4.0.
- Licence:
- CC Attribution (CC BY)
If you are the owner of this record, you can report an update to it here: Report update to this record