#include "hrichIPUremake.h" |
HRichIPURemake
class description - source file - inheritance tree (.pdf)
private:
Bool_t initParContainer(HSpectrometer*, HRuntimeDb*)
public:
HRichIPURemake()
HRichIPURemake(Text_t* name, Text_t* title)
~HRichIPURemake()
static TClass* Class()
virtual Int_t execute()
virtual Bool_t finalize()
virtual Bool_t init()
virtual TClass* IsA() const
void prepareInput()
virtual void ShowMembers(TMemberInspector& insp, char* parent)
virtual void Streamer(TBuffer& b)
void StreamerNVirtual(TBuffer& b)
protected:
HCategory* pRich !
HRichIPUParThresholds* fRichIPUParThr !
HRichIPUParLocMax* fRichIPUParLmax !
HIterator* iterRich !
Bool_t initParContainer(HSpectrometer *spec, HRuntimeDb *rtdb)
Adds to the runtime database "rtdb" the containers needed by the MU Emulation
spec is used to get information of the spectrometer setup.
HRichIPURemake(void)
Default constructor
Input parameters:
none
Output parameters:
none
Return code:
none
HRichIPURemake(Text_t *name,Text_t *title)
: HReconstructor(name, title)
Default constructor
Input parameters:
Text_t *name
Name of the object
Text_t *title
Title of the object
Output parameters:
none
Return code:
none
~HRichIPURemake(void)
Destructor
Delete the iterators
Input parameters:
none
Output parameters:
none
Return code:
none
Bool_t init(void)
Int_t execute(void)
Execute the job.
Input parameters:
none
Output parameters:
none
Return code:
Allways 0.
void prepareInput(void)
Get all needed data from the category into the internal datastructures.
Input parameters:
none
Output parameters:
none
Return code:
none
Bool_t finalize(void)
Finalize the job.
Input parameters:
none
Output parameters:
none
Return code:
Returns allways kTRUE;
Inline Functions
TClass* Class()
TClass* IsA() const
void ShowMembers(TMemberInspector& insp, char* parent)
void Streamer(TBuffer& b)
void StreamerNVirtual(TBuffer& b)
Last update: Fri Jan 26 12:27:58 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.