CMS 3D CMS Logo

List of all members | Public Member Functions | Public Attributes
customisers.module_manipulate Class Reference

Customizer for skimming ########################### There are four different parts. More...

Public Member Functions

def __init__ (self, module_name, manipulator_name, steps=["SELECT","CLEAN","SIM","MERGE"], instance=[""], merge_prefix="")
 

Public Attributes

 cleaner_name
 
 instance
 
 manipulator_name
 
 merge_prefix
 
 merger_name
 
 module_name
 
 steps
 

Detailed Description

Customizer for skimming ########################### There are four different parts.

First step is the SELECT (former SKIM) part, where we identfy the events which are good for Embedding. Need to store RAWRECO [RAW is needed for the MERG and RECO for the CLEAN step] Second step is the CLEAN input are PAT muons with RECO information. After this step only RAW plus some special collections needed for the MERG step must be saved Third step is the SIM. The input is the externalLHEProducer, which must be produced before (At the moment we do it parallel to the CLEAN step). Again only save RAW of the SELECT and only save what is need for the MERG step Last step is the MERG step. Which is the usally reconstruction, where the input produces are replaced by merg producer, which mix the SIM and CLEAN inputs. Some comments on this approach. All steps runs the RECO sequence until the end in the moment. It would be possible to stop after the all inputs which are needed for the MERG step are generated (which happens at a very early state of the reconstruction. But with this approach we are able to get the RECO (and PAT aka miniAOD) of all four step SELECT (orginal event), SIM, CLEAN and MERGED. Therefor one only needs to SAVE the corresponding output (in cmsDriver change output to RAW -> RAW,RECO,PAT) Some basic functions #################### Helper Class, which summerizes in which step which Producer (Cleaner Merger), should be loaded. It is also usefull to define which collection should be stored for the next step E.g What is needed for MERGE must be produce in the CLEAN and SIM step

Definition at line 24 of file customisers.py.

Constructor & Destructor Documentation

◆ __init__()

def customisers.module_manipulate.__init__ (   self,
  module_name,
  manipulator_name,
  steps = ["SELECT","CLEAN","SIM","MERGE"],
  instance = [""],
  merge_prefix = "" 
)

Definition at line 25 of file customisers.py.

25  def __init__(self, module_name, manipulator_name, steps = ["SELECT","CLEAN","SIM","MERGE"], instance=[""], merge_prefix = ""):
26  self.module_name = module_name
27  self.manipulator_name = manipulator_name
28  self.steps = steps
29  self.instance = instance
30  self.merger_name = manipulator_name+"ColMerger"
31  self.cleaner_name = manipulator_name+"ColCleaner"
32  self.merge_prefix = merge_prefix
33 
34 
35 
36 

Member Data Documentation

◆ cleaner_name

customisers.module_manipulate.cleaner_name

Definition at line 31 of file customisers.py.

◆ instance

customisers.module_manipulate.instance

Definition at line 29 of file customisers.py.

◆ manipulator_name

customisers.module_manipulate.manipulator_name

Definition at line 27 of file customisers.py.

◆ merge_prefix

customisers.module_manipulate.merge_prefix

Definition at line 32 of file customisers.py.

◆ merger_name

customisers.module_manipulate.merger_name

Definition at line 30 of file customisers.py.

◆ module_name

customisers.module_manipulate.module_name

Definition at line 26 of file customisers.py.

◆ steps

customisers.module_manipulate.steps

Definition at line 28 of file customisers.py.