Journal article icon

Journal article

Measurement and interpretation of same-sign W boson pair production in association with two jets in pp collisions at s = 13 TeV with the ATLAS detector

Abstract:
This paper presents the measurement of fiducial and differential cross sections for both the inclusive and electroweak production of a same-sign W-boson pair in association with two jets (W±W±jj) using 139 fb−1 of proton-proton collision data recorded at a centre-of-mass energy of s = 13 TeV by the ATLAS detector at the Large Hadron Collider. The analysis is performed by selecting two same-charge leptons, electron or muon, and at least two jets with large invariant mass and a large rapidity difference. The measured fiducial cross sections for electroweak and inclusive W±W±jj production are 2.92 ± 0.22 (stat.) ± 0.19 (syst.) fb and 3.38 ± 0.22 (stat.) ± 0.19 (syst.) fb, respectively, in agreement with Standard Model predictions. The measurements are used to constrain anomalous quartic gauge couplings by extracting 95% confidence level intervals on dimension-8 operators. A search for doubly charged Higgs bosons H±± that are produced in vector-boson fusion processes and decay into a same-sign W boson pair is performed. The largest deviation from the Standard Model occurs for an H±± mass near 450 GeV, with a global significance of 2.5 standard deviations.
Publication status:
Published
Peer review status:
Peer reviewed

Actions

Access Document

Publisher copy:
10.1007/jhep04(2024)026

Authors


Publisher:
Springer
Journal:
Journal of High Energy Physics More from this journal
Volume:
2024
Issue:
4
Article number:
26
Publication date:
2024-04-04
Acceptance date:
2024-03-04
DOI:
EISSN:
1029-8479


Language:
English
Keywords:
Pubs id:
1988952
Local pid:
pubs:1988952
Source identifiers:
2136955
Deposit date:
2024-07-25
ARK identifier:
This ORA record was generated from metadata provided by an external service. It has not been edited by the ORA Team.

Terms of use


Views and Downloads






If you are the owner of this record, you can report an update to it here: Report update to this record

TO TOP