REVIEW 3 cited by
Which Metric on the Space of Collider Events?
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
Signed reviews
read the original abstract
Which is the best metric for the space of collider events? Motivated by the success of the Energy Mover's Distance in characterizing collider events, we explore the larger space of unbalanced optimal transport distances, of which the Energy Mover's Distance is a particular case. Geometric and computational considerations favor an unbalanced optimal transport distance known as the Hellinger-Kantorovich distance, which possesses a Riemannian structure that lends itself to efficient linearization. We develop the particle linearized unbalanced Optimal Transport (pluOT) framework for collider events based on the linearized Hellinger-Kantorovich distance and demonstrate its efficacy in boosted jet tagging. This provides a flexible and computationally efficient optimal transport framework ideally suited for collider physics applications.
Forward citations
Cited by 3 Pith papers
-
Generative Amplification with Surrogate Monte Carlo
An amplitude surrogate trained on a few thousand exact LHC amplitude points statistically outperforms the training data, with largest amplification in sparsely populated kinematic tails of Z+g and Z+4g production.
-
Factorization for Collider Dataspace Correlators
Derives a factorization theorem and NLL resummation for SEMD-based event correlators, predicting a universal ledge in quark-jet non-Gaussianity.
-
A Step Toward Interpretability: Smearing the Likelihood
Smearing the likelihood over an energy metric reveals the physical scales used by a jet classifier, and the needed smearing radius follows a power-law scaling with dataset size.
Discussion (0). Continue with ORCID to comment.