ATLAS Offline Software
Classes | Functions
T_AnalysisConfigR3_Tier0.h File Reference

baseclass template so that we can use in different contexts in different ways in the monitoring More...

#include "TrigInDetAnalysis/TIDAEvent.h"
#include "TrigInDetAnalysis/TIDAVertex.h"
#include "TrigInDetAnalysis/TrackSelector.h"
#include "TrigInDetAnalysisUtils/T_AnalysisConfig.h"
#include "TrigInDetAnalysisUtils/TagNProbe.h"
#include "TrigInDetAnalysisExample/AnalysisR3_Tier0.h"
#include "TrigInDetAnalysisExample/VtxAnalysis.h"
#include "TrigInDetAnalysisExample/ChainString.h"
#include "TrigInDetAnalysisExample/TIDATools.h"
#include "TTree.h"
#include "TFile.h"
#include "GaudiKernel/ToolHandle.h"
#include "AthenaMonitoringKernel/GenericMonitoringTool.h"
#include "McParticleEvent/TruthParticleContainer.h"
#include "GeneratorObjects/McEventCollection.h"
#include "AtlasHepMC/GenEvent.h"
#include "AtlasHepMC/GenVertex.h"
#include "AtlasHepMC/GenParticle.h"
#include "xAODEventInfo/EventInfo.h"
#include "TrigInDetAnalysis/TIDDirectory.h"
#include "TrigInDetAnalysis/Filter_AcceptAll.h"
#include "TrigInDetAnalysisUtils/TIDARoiDescriptorBuilder.h"
#include "TrigInDetAnalysisUtils/Filter_etaPT.h"
#include "TrigInDetAnalysisUtils/Filter_RoiSelector.h"
#include "TrigInDetAnalysisUtils/Associator_BestMatch.h"
#include "TrigInDetAnalysisUtils/Filters.h"
#include "VxVertex/VxContainer.h"
#include "muonEvent/MuonContainer.h"
#include "egammaEvent/ElectronContainer.h"
#include "tauEvent/TauJetContainer.h"
#include "TrigSteeringEvent/HLTResult.h"
#include "TrigDecisionTool/ExpertMethods.h"
#include "xAODTracking/TrackParticle.h"
#include "xAODTracking/TrackParticleContainer.h"
#include "TrigCompositeUtils/TrigCompositeUtils.h"
This graph shows which files directly or indirectly include this file:

Go to the source code of this file.

Classes

class  T_AnalysisConfigR3_Tier0< T, A >
 

Functions

template<typename T >
std::ostream & operator<< (std::ostream &s, const std::vector< T > &v)
 

Detailed Description

baseclass template so that we can use in different contexts in different ways in the monitoring

NB: this will be configured to run either a standard analysis, or a "purity" analysis. If a purity analysis, the trigger tracks become the reference (with all the selection) and the offline or truth the "test" tracks This would be a simple switch if the reference tracks were in the RoI, but as they are not we need to move the RoI filtering to the test filter and not the reference filter grrrrrr

Author
mark sutton
Date
Tue 16 May 2017 09:28:55 CEST

Copyright (C) 2002-2024 CERN for the benefit of the ATLAS collaboration

Definition in file T_AnalysisConfigR3_Tier0.h.

Function Documentation

◆ operator<<()

template<typename T >
std::ostream& operator<< ( std::ostream &  s,
const std::vector< T > &  v 
)

Definition at line 89 of file T_AnalysisConfigR3_Tier0.h.

89  {
90  for ( size_t i=0 ; i<v.size() ; i++ ) s << " " << v[i];
91  return s;
92 }
python.SystemOfUnits.s
int s
Definition: SystemOfUnits.py:131
lumiFormat.i
int i
Definition: lumiFormat.py:85
python.PyAthena.v
v
Definition: PyAthena.py:154