REVIEW 2 cited by
Multi-messenger connection in high-energy neutrino astronomy
Not yet reviewed by Pith; the record is open.
This paper has not been read by Pith yet. Machine review is queued; the pith claim, tier, and objections will appear here once it completes.
SPECIMEN: schema-true, not a live event
T0 review · schema-true
One-sentence machine reading of the paper's core claim.
pith:XXXXXXXX · record.json · timestamp
read the original abstract
Low fluxes of astrophysical neutrinos at TeV energies and the overwhelming background of atmospheric neutrinos below that, render the current paradigm of neutrino astronomy as a severely statistics limited one. While many hints have emerged, all the evidence gathered by IceCube and ANTARES, over the course of almost a decade and a half of operation, have fallen short of providing any conclusive answer to the puzzle of the origin of high-energy cosmic rays and neutrinos. The advancement of the field is thus closely associated with not only the neutrino observatories coming online in the next few years, but also on the coordinated efforts of the EM, GW and cosmic ray communities to develop dedicated channels and infrastructure that allows for swift and comprehensive multi-messenger follow-up of relevant events detected in any of the sectors. This paper highlights the strides that have been already taken in that direction and the fruits that they have born, as well as the challenges that lie ahead.
Forward citations
Cited by 2 Pith papers
-
Strong field gravitational lensing of particles by a black-bounce-Schwarzschild black hole
For a black-bounce-Schwarzschild black hole, the paper derives the strong-deflection lensing observables for massive particles and quantifies how they differ from photon lensing.
-
Blazars Jets and prospects for TeV-PeV neutrinos & gamma-rays through cosmic-ray interactions
A single-zone model with added proton-proton collisions suggests W Comae and 1ES 1959+650 need hadronic emission, and CTAO sensitivity forecasts show all four BL Lacs are detectable.
Discussion (0). Continue with ORCID to comment.