Journal article
Search for a new pseudoscalar decaying into a pair of bottom and antibottom quarks in top-associated production in $$\sqrt{s}=13$$ TeV proton–proton collisions with the ATLAS detector
- Abstract:
- Abstract A search for a pseudoscalar a produced in association with a top-quark pair, or in association with a single top quark plus a W boson, with the pseudoscalar decaying into b -quarks ( $$a\rightarrow b\bar{b}$$ a → b b ¯ ), is performed using the full Run 2 data sample using a dileptonic decay mode signature. The search covers pseudoscalar boson masses between 12 and 100 GeV and involves both the kinematic regime where the decay products of the pseudoscalar are reconstructed as two standard b -tagged small-radius jets, or merged into a large-radius jet due to its Lorentz boost. No significant excess relative to expectations is observed. Assuming a branching ratio $$\text {BR}(a\rightarrow b\bar{b})=100\% $$ BR ( a → b b ¯ ) = 100 % , the range of pseudoscalar masses between 50 and 80 GeV is excluded at 95% confidence level for a coupling of the pseudoscalar to the top quark of 0.5, while a coupling of 1.0 is excluded at 95% confidence level for the masses considered, with the coupling defined as the strength modifier of the Standard Model Yukawa coupling.
- Publication status:
- Published
- Peer review status:
- Peer reviewed
Actions
Access Document
- Files:
-
-
(Preview, Version of record, pdf, 5.1MB, Terms of use)
-
- Publisher copy:
- 10.1140/epjc/s10052-025-14507-0
Authors
- Publisher:
- SpringerOpen
- Journal:
- The European Physical Journal C More from this journal
- Volume:
- 85
- Issue:
- 8
- Article number:
- 886
- Publication date:
- 2025-08-19
- DOI:
- EISSN:
-
1434-6052
- ISSN:
-
1434-6044
- Language:
-
English
- Keywords:
- Pubs id:
-
2283754
- Local pid:
-
pubs:2283754
- Source identifiers:
-
W4413326999
- Deposit date:
-
2025-08-23
This ORA record was generated from metadata provided by an external service. It has not been edited by the ORA Team.
If you are the owner of this record, you can report an update to it here: Report update to this record