#include "hrpcunpacker.h" |
HRpcUnpacker
class description - source file - inheritance tree (.pdf)
public:
HRpcUnpacker(UInt_t id = 0x222, Bool_t unpaired = kFALSE, Int_t dbg = 0)
HRpcUnpacker(const HRpcUnpacker&)
~HRpcUnpacker()
static TClass* Class()
virtual Int_t execute()
virtual Int_t getSubEvtId() const
virtual Bool_t init()
virtual TClass* IsA() const
HRpcUnpacker& operator=(const HRpcUnpacker&)
virtual void ShowMembers(TMemberInspector& insp, char* parent)
virtual void Streamer(TBuffer& b)
void StreamerNVirtual(TBuffer& b)
protected:
UInt_t subEvtId
Bool_t isUnpaired
Int_t debug
HLocation loc
HRpcLookup* lookup
HRpcUnpacker
This is the unpacker used to read for the first time the RPC data
(see RpcDataStructure in WIKI for subevent information)
This unpacker is quite robust and returns quite a lot of info for debugging
The unpacker accepts the following arguments:
HRpcUnpacker(UInt_t id, Bool_t unpaired, Int_t dbg)
where:
id is the subEvent Id
unpaired=kTRUE selects the unpaired mode of the TDCs in the TRB
(the default value is unpaired=kFALSE)
debug controls the debugging level and the number of messages
debug=0 only relevant errors (show-stoppers)
debug=1 warning and all errors are on
debug=2 additional information on read words
debug=3 full decoding
HRpcUnpacker(UInt_t id, Bool_t unpaired, Int_t dbg)
constructor
Bool_t init(void)
creates the raw category and gets the pointer to the lookup table
Int_t execute()
This function fills the RPC raw data structure.
---------------------------------------------------------------------
Inline Functions
void ~HRpcUnpacker()
Int_t getSubEvtId() const
TClass* Class()
TClass* IsA() const
void ShowMembers(TMemberInspector& insp, char* parent)
void Streamer(TBuffer& b)
void StreamerNVirtual(TBuffer& b)
HRpcUnpacker HRpcUnpacker(const HRpcUnpacker&)
HRpcUnpacker& operator=(const HRpcUnpacker&)
Last update: Fri Jan 26 12:30:48 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.