JetMaker


Purpose

To cover the functionality of smearing the Cluster formed by ClusterMaker and to complete the Jet construction by adding non-isolated muons.
The existence of a class responsible for jet construction allows the implementation of a range of Jet Finders, according to future new users requirements.

Jet Definition


Jets are Clusters which have not been associated with isolated particles (electrons or photons) and which then pass some pre-defined kinematic criteria.
In order to form Jets, JetMaker smears the cluster four-momentum, adds non-isolated muons which falls in a predefined R-cone around the Jet and tag the Jet with a flavour.
The JetCandidate is kept and labelled as a reconstructed Jet if its energy is greater than a given threshold and its eta passes the eta fiducial cut.
Options for low and high luminosity allow to tune the smearer algorithm, adding to the smearing function a pile-up effect for high luminosity.

JetMaker Overview

The default jet finder algorithm builds jets from cells not in the clusters, clusters and non-isolated muons.
Then it performs the following operations:
  1. Obtains all clusters from the Transient Event Store (TES)
  2. Obtains all non-isolated muons from TES.
  3. Examines all Clusters, and retains only those not associated with isolated electrons and isolated photons.
  4. Creates a JetCandidates by smearing the four-momentum of the Cluster. A JetSmearer object encapsulates the parametrization of this operation.
  5. Finds the nearest non-isolated muon to the Jet direction: if it is within a cone of radius R = 0.4 (the actual value is the same for the barrel and the forward region, but different data can be implemented), it is added to the Jet.
    This muon is then removed from the vector of muons available to further jet construction for that event.
  6. A JetCandidate is made, which is checked for passing kinematic cuts on Et and eta, Et > 10 and eta < 5.0;
  7. The HepMC structure is scanned for a tau-meson or a heavy quark which could tag the Jet.
    If none of these tags are found, the jet is labelled as u-quark.
  8. The tagged Jet is then ouput to the TES.

JetMaker uses the helper class TesIO to perform input/output operations from the TES.

User Requirements Satisfied

The design fulfills requirements of Sec 3.1.5 of the ARD.

JetMaker Detail

jobOptions Properties

jobOptions properties are steering parameters which can be set by the user in the jobOptions file.
They are declared in the constructor and initialised to Default Values.
The options for this algorithm are:



Initialisation

The initialise method is called once at the beginning of the job.


Execute Sequence

JetMaker execution sequence diagram

Class Diagram

The various classes discussed above are shown in the class diagram.
JetMaker class diagram