REVIEW 2 cited by
Measurement of dijet production with a veto on additional central jet activity in pp collisions at sqrt(s)=7 TeV using the ATLAS detector
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
A measurement of jet activity in the rapidity interval bounded by a dijet system is presented. Events are vetoed if a jet with transverse momentum greater than 20 GeV is found between the two boundary jets. The fraction of dijet events that survive the jet veto is presented for boundary jets that are separated by up to six units of rapidity and with mean transverse momentum 50 < pT(avg) < 500 GeV. The mean multiplicity of jets above the veto scale in the rapidity interval bounded by the dijet system is also presented as an alternative method for quantifying perturbative QCD emission. The data are compared to a next-to-leading order plus parton shower prediction from the POWHEG-BOX, an all-order resummation using the HEJ calculation and the PYTHIA, HERWIG++ and ALPGEN event generators. The measurement was performed using pp collisions at sqrt(s)=7 TeV using data recorded by the ATLAS detector in 2010.
Forward citations
Cited by 2 Pith papers
-
Super-Leading Logarithms in $pp\to2$ Jets
Super-leading logarithms contribute about 13 percent to the LHC pp to 2 jets gap-between-jets cross section at Q0 = 10 GeV, and a q qbar interference term is only 1/Nc suppressed.
-
Endpoint Logarithms in the NLO Mueller-Navelet Jet Vertex: Threshold Matching and BLM/MOM Prescription Sensitivity
A conservative BFKL-aware threshold matching scheme is constructed for the NLO forward jet vertex that resums ordinary endpoint logs, preserves NLO accuracy, and is tested against CMS azimuthal observables, showing in...
Discussion (0). Continue with ORCID to comment.