Journal article
Search for charged Higgs bosons decaying into a top quark and a bottom quark at $$ \sqrt{\mathrm{s}} $$ = 13 TeV with the ATLAS detector
- Abstract:
- A bstract A search for charged Higgs bosons decaying into a top quark and a bottom quark is presented. The data analysed correspond to 139 fb − 1 of proton-proton collisions at $$ \sqrt{s} $$ s = 13 TeV, recorded with the ATLAS detector at the LHC. The production of a heavy charged Higgs boson in association with a top quark and a bottom quark, pp → tbH + → tbtb , is explored in the H + mass range from 200 to 2000 GeV using final states with jets and one electron or muon. Events are categorised according to the multiplicity of jets and b -tagged jets, and multivariate analysis techniques are used to discriminate between signal and background events. No significant excess above the background-only hypothesis is observed and exclusion limits are derived for the production cross-section times branching ratio of a charged Higgs boson as a function of its mass; they range from 3.6 pb at 200 GeV to 0.036 pb at 2000 GeV at 95% confidence level. The results are interpreted in the hMSSM and $$ {M}_h^{125} $$ M h 125 scenarios.
- Publication status:
- Published
- Peer review status:
- Peer reviewed
Actions
Access Document
- Files:
-
-
(Preview, Version of record, pdf, 2.7MB, Terms of use)
-
- Publisher copy:
- 10.1007/jhep06(2021)145
Authors
- Publisher:
- Springer
- Journal:
- Journal of High Energy Physics More from this journal
- Volume:
- 2021
- Issue:
- 6
- Pages:
- 145
- Article number:
- 145
- Publication date:
- 2021-06-24
- DOI:
- EISSN:
-
1029-8479
- ISSN:
-
1126-6708
- Language:
-
English
- Keywords:
- Pubs id:
-
1185573
- Local pid:
-
pubs:1185573
- Source identifiers:
-
W2887397961
- Deposit date:
-
2026-03-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
- Copyright date:
- 2021
- 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