#include "hpidparticlefiller.h" |
HPidParticleFiller
class description - source file - inheritance tree (.pdf)
public:
HPidParticleFiller(Option_t* par)
HPidParticleFiller(Text_t* name, Text_t* title, Option_t* par)
~HPidParticleFiller()
void addAlgorithm(Int_t iAId)
virtual Bool_t buildOutputCategory(Bool_t makeSimCategory = kFALSE)
virtual Int_t checkCandidate(HPidCandidate* pCand)
static TClass* Class()
virtual Int_t execute()
virtual Bool_t finalize()
Int_t getAlgorithm() const
Int_t getDebug() const
virtual HPidParticle* getNextSlot()
Bool_t getUseMassExp() const
virtual Bool_t init()
virtual TClass* IsA() const
virtual void Print(Option_t* option) const
virtual void print() const
virtual Bool_t reinit()
void removeAlgorithm(Int_t iAId)
void setAlgorithm(Int_t i)
void setDebug(Int_t i)
void setDefault()
virtual void setParameters(Option_t* par)
void setUseMassExp(Bool_t b)
virtual void ShowMembers(TMemberInspector& insp, char* parent)
virtual void Streamer(TBuffer& b)
void StreamerNVirtual(TBuffer& b)
protected:
HCategory* pInputCat category of HPidCandidate
HIterator* pitInput iterator on the pInputCat category
HCategory* pOutCat category of HPidParticle
Int_t iAlgorithm algoritm used in computation of merged probability - could be algBayes or algLikelyhood
Bool_t bIncludeFakes should fakes be included into calculation?
Bool_t bMakeSimCategory should the sim or real category be made ?
Bool_t bUseMassExp if massExp should fill TLorentzVector
TArrayI aAlgorithms list of algorithms for Bayes and Merging
TArrayF aCandValues array for the candidate values
Int_t iMomAlg algorithm used for momentum reconstruction of the particle
Int_t iDebug debug level
static HPidParticleFiller* pCurPartFiller
HPidParticleFiller
Filler of HPidParticle category from the data in HPidCandidate.
This reconstructor loops over all HPidCandidates and builds HPidParticles
from them. The procedure is as follows:
1. Pick a HPidCandidate
2. Get merged PDF or full Bayesian probability from the Candidate
HPidParticleFiller(Option_t par[])
: HReconstructor("PidPartFiller",
"Filler of HPidParticle category")
Default constructor.
HPidParticleFiller(Text_t name[], Text_t title[],
Option_t par[])
: HReconstructor(name, title)
Constructor with names
~HPidParticleFiller(void)
Destructor
void setDefault(void) //OK
Called in constructors to set default valuest to the members
Bool_t init(void)//OK
Build all categories
Bool_t reinit(void) //OK
Check the reconstructor parameters
Bool_t buildOutputCategory(Bool_t makeSimCategory) //OK
Check the output class and build output category for it.
void setParameters(Option_t par[]) //OK
Set parameters by names. Options (may be separated by comma or blank chars):
DEBUGX - debug info, if X set then it define the debug info level
MASSEXP - use experimental mass to fill TLorentzVector
MAKESIMCATEGORY - fill simulation objects (HPidParticleSim)
INCLUDEFAKES - consider "fake" as a species as which a particle can be identified
SPLINE/KICK/KICK123
void addAlgorithm(Int_t iAId) //OK
void removeAlgorithm(Int_t iAId) //OK
Int_t execute(void)//OK
HPidParticle* getNextSlot(void) //OK
Get next slot from the output category
Int_t checkCandidate(HPidCandidate *pCand) //OK
Check if pCand has a good quality and fills the HPidParticle for it.
The HKickTrack correlated with the HPidCandidate must be available.
The method returns number of HPidParticle created for the pCand.
void print(void) const
Not implemented
Inline Functions
Bool_t finalize()
void setAlgorithm(Int_t i)
Int_t getAlgorithm() const
Int_t getDebug() const
void setDebug(Int_t i)
void setUseMassExp(Bool_t b)
Bool_t getUseMassExp() const
void Print(Option_t* option) const
TClass* Class()
TClass* IsA() const
void ShowMembers(TMemberInspector& insp, char* parent)
void Streamer(TBuffer& b)
void StreamerNVirtual(TBuffer& b)
Author: Marcin Jaskula 30/10/2002
Last update: Fri Jan 26 12:22:42 2007
ROOT page - Class index - Class Hierarchy - Top of the page
This page has been automatically generated. If you have any comments or suggestions about the page layout send a mail to ROOT support, or contact the developers with any questions or problems regarding ROOT.