Fork me on GitHub

Opened 8 years ago

#1065 new How to

Question regarding jet constituents and jet trimming (ATLAS card)

Reported by: Wojtek Fedorko Owned by:
Priority: minor Milestone:
Component: Delphes code Version: Delphes 3
Keywords: jet trimming, constituents, fat jets Cc:

Description

Hello,
I starting from the delphes_ATLAS_card_Pileup.tcl I modified the FastJetFinder configuration as following since I want to study substructure of fat jets after trimming:

module FastJetFinder FastJetFinder {
  set InputArray Calorimeter/towers

  set OutputArray jets

  # area algorithm: 0 Do not compute area, 1 Active area explicit ghosts, 2 One ghost passive area, 3 Passive area, 4 Voronoi, 5 Active area
    #set AreaAlgorithm 5
  #set AreaAlgorithm 0

  # jet algorithm: 1 CDFJetClu, 2 MidPoint, 3 SIScone, 4 kt, 5 Cambridge/Aachen, 6 antikt
  set JetAlgorithm 6
  set ParameterR 1.0

  set ComputeTrimming 1
  set RTrim 0.2
  set PtFracTrim 0.05  

  set JetPTMin 20.0
}

and I left the rest of the 'chain' without changes.
My question is if the jet constituents (Towers) are 'after' trimming are being stored? At the analysis stage when I access the constituents I see a lot of very low ET towers and I expected it to be more 'cleaned up' by trimming.
I access the constituent towers (in python) like this: (loosely based on Example3.C):

towers = jet.Constituents

(and I don't do a typecheck any more as they are all of Tower type)

Is there anything special I'd need to do to access only the constituents after trimming?

Thank you for clarifying this,
Wojtek

Change History (0)

Note: See TracTickets for help on using tickets.