Papers › IceCube -- Neutrinos in Deep Ice The Top 3 Solutions from the Public Kaggle Competition

IceCube -- Neutrinos in Deep Ice The Top 3 Solutions from the Public Kaggle Competition

24 Oct 2023arXiv:2310.15674links table onlyarchive 2025-07-28

Habib Bukhari, Dipam Chakraborty, Philipp Eller, Takuya Ito, Maxim V. Shugaev, Rasmus Ørsøe

The archive published only this paper's code-link row. Authors, date and abstract are from arXiv's metadata (CC0), read from the Kaggle arXiv metadata snapshot of 2026-09-12 where its title matched the archive's; the title is the archive's.

During the public Kaggle competition "IceCube -- Neutrinos in Deep Ice", thousands of reconstruction algorithms were created and submitted, aiming to estimate the direction of neutrino events recorded by the IceCube detector. Here we describe in detail the three ultimate best, award-winning solutions. The data handling, architecture, and training process of each of these machine learning models is laid out, followed up by an in-depth comparison of the performance on the kaggle datatset. We show that on cascade events in IceCube above 10 TeV, the best kaggle solution is able to achieve an angular resolution of better than 5 degrees, and for tracks correspondingly better than 0.5 degrees. These performance measures compare favourably to the current state-of-the-art in the field.

PaperPDFCode

Code

dipamc/kaggle-icecube-neutrinos officialmentioned in papermentioned on GitHubpytorch report

Repository list and official/mentioned flags are the archive's, frozen 2025-07-28. Reachability, where shown, is from one Syntology probe window (2026-09-16 to 2026-09-18); repositories not probed show nothing. GitHub stars are not tracked.

Code Syntology ran Syntology

Not run by Syntology. Nothing on this page verifies that the listed code works.

Results from the paper archive 2025-07-28

No leaderboard rows for this paper in the archive.

Report a problem or propose a change · a person checks every report against the paper or source before anything changes; decisions are listed on /corrections