dorsal/arxiv
View SchemaBose-Einstein Correlations from Random Walk Models
| Authors | Boris Tomasik, Ulrich Heinz, Jan Pisut |
|---|---|
| Categories | |
| ArXiv ID | nucl-th/9711013 |
| URL | https://arxiv.org/abs/nucl-th/9711013 |
| DOI | 10.1016/S0370-2693(98)00179-8 |
| Journal | Phys.Lett.B425:145-150,1998 |
Abstract
We argue that strong final state rescattering among the secondary particles created in relativistic heavy ion collisions is essential to understand the measured Bose-Einstein correlations. The recently suggested ``random walk models'' which contain only initial state scattering are unable to reproduce the measured magnitude and K_\perp-dependence of R_\perp in Pb+Pb collisions and the increase of R_l with increasing size of the collision system.
{
"annotation_id": "ade20f8b-654e-465a-b9fb-31b2bea9c717",
"date_created": "2026-03-02T18:00:21.984000Z",
"date_modified": "2026-03-02T18:00:21.984000Z",
"file_hash": "bddfa99432da8e23d639816395027e79e2ad7043db9f97ce022d1d9ca92629c7",
"private": false,
"record": {
"abstract": "We argue that strong final state rescattering among the secondary particles\ncreated in relativistic heavy ion collisions is essential to understand the\nmeasured Bose-Einstein correlations. The recently suggested ``random walk\nmodels\u0027\u0027 which contain only initial state scattering are unable to reproduce\nthe measured magnitude and K_\\perp-dependence of R_\\perp in Pb+Pb collisions\nand the increase of R_l with increasing size of the collision system.",
"arxiv_id": "nucl-th/9711013",
"authors": [
"Boris Tomasik",
"Ulrich Heinz",
"Jan Pisut"
],
"categories": [
"nucl-th",
"hep-ph"
],
"doi": "10.1016/S0370-2693(98)00179-8",
"journal_ref": "Phys.Lett.B425:145-150,1998",
"title": "Bose-Einstein Correlations from Random Walk Models",
"url": "https://arxiv.org/abs/nucl-th/9711013"
},
"schema_id": "dorsal/arxiv",
"source": {
"execution_id": "64e66dfa-e133-42e9-82c6-d49b02d8d1b9",
"id": "arXiv Dataset IDs",
"type": "Model",
"variant": "snapshot-2026-03-01",
"version": "0.1.0"
},
"user_id": 1000002
}