* analysis publish new data for the subsequent components. Only the
* input data blocks and entries from CDB are available for the analysis.
*
- * @section alihlt_component_intro Component implementation
+ * @section alihlt_component_implementation Component implementation
* AliHLTComponent provides the interface for all components, see there
* for details. Three types are provided:
* - AliHLTProcessor
class TStopwatch;
class AliHLTComponent;
class AliHLTMemoryFile;
+class AliHLTCTPData;
/** list of component data type structures */
typedef vector<AliHLTComponentDataType> AliHLTComponentDataTypeList;
* If the component has multiple output data types @ref GetOutputDataType
* should return @ref kAliHLTMultipleDataType. The framework will invoke
* @ref GetOutputDataTypes, a list can be filled.
+ * - @ref Reconfigure
+ * This function is invoked by the framework on a special event which
+ * triggers the reconfiguration of the component.
*
* @subsection alihltcomponent-processing-mehods Data processing
*
* framework will allocate a buffer of appropriate size and call the processing
* again.
*
- * @subsection alihltcomponent-error-codes Data processing
+ * @subsection alihltcomponent-error-codes Return values/Error codes
* For return codes, the following scheme applies:
* - The data processing methods have to indicate error conditions by a negative
* error/return code. Preferably the system error codes are used like
* <pre>
* \#include \<cerrno\>
* </pre>
+ * This schema aplies to all interface functions of the component base class.
+ * For data processing it is as follows:
* - If no suitable input block could be found (e.g. no clusters for the TPC cluster
* finder) set size to 0, block list is empty, return 0
* - If no ususable or significant signal could be found in the input blocks
* - @ref AliHLTDataSource::GetEvent
* - @ref AliHLTDataSink::DumpEvent
*
- *
+ * The base class passes all relevant parameters for data access directly on to the
+ * component. Input blocks can be accessed by means of the array <tt> blocks </tt>.
+ * Output data are written directly to shared memory provided by the pointer
+ * <tt> outputPtr </tt> and output block descriptors are inserted directly to the
+ * list <tt> outputBlocks </tt>.
+ *
+ * \b NOTE: The high-level input data access methods can be used also from the low
+ * level interface. Also the PushBack functions can be used BUT ONLY if no data is
+ * written to the output buffer and no data block descriptors are inserted into the
+ * output block list.
+ *
+ * @section alihltcomponent-initialization Component initialization and configuration
+ * The component interface provides two optional methods for component initialization
+ * and configuration. The @ref DoInit function is called once before the processing.
+ * During the event processing, a special event can trigger a reconfiguration and the
+ * @ref Reconfigure method is called. There are three possible options of initialization
+ * and configuration:
+ * - default values: set directly in the source code
+ * - OCDB objects: all necessary information must be loaded from OCDB objects. The
+ * Offline Conditions Data Base stores objects specifically valid for individual runs
+ * or run ranges.
+ * - Component arguments: can be specified for every component in the chain
+ * configuration. The arguments can be used to override specific parameters of the
+ * component.
+ *
+ * As a general rule, the three options should be processed in that sequence, i.e
+ * default parameters might be overridden by OCDB configuration, and the latter one
+ * by component arguments.
+ *
+ * @subsection alihltcomponent-initialization-arguments Component arguments
+ * In normal operation, components are supposed to run without any additional argument,
+ * however such arguments can be useful for testing and debugging. The idea follows
+ * the format of command line arguments. A keyword is indicated by a dash and an
+ * optional argument might follow, e.g.:
+ * <pre>
+ * -argument1 0.5 -argument2
+ * </pre>
+ * In this case argument1 requires an additional parameter whereas argument2 does not.
+ * The arguments will be provided as an array of separated arguments.
+ *
+ * Component arguments can be classified into initialization arguments and configuration
+ * arguments. The latter are applicable for both the @ref DoInit and @ref Reconfigure
+ * method whereas initialization arguments are not applicable after DoInit.
+ *
+ * @subsection alihltcomponent-initialization-ocdb OCDB objects
+ * OCDB objects are ROOT <tt>TObjects</tt> and can be of any type. This is in particular
+ * useful for complex parameter sets. However in most cases, a simple approach of human
+ * readable command line arguments is appropriate. Such a string can be simply stored
+ * in a TObjString (take note that the TString does not derive from TObject). The
+ * same arguments as for the command line can be used. Take note that in the TObjString
+ * all arguments are separated by blanks, instead of being in an array of separate
+ * strings.
+ *
+ * The base class provides two functions regarding OCDB objects:
+ * - LoadAndExtractOCDBObject() loads the OCDB entry for the specified path and extracts
+ * the TObject from it.
+ * - ConfigureFromCDBTObjString() can load a number of OCDB objects and calls the
+ * argument parsing ConfigureFromArgumentString
+ *
+ *
+ * @subsection alihltcomponent-initialization-sequence Initialization sequence
+ * Using the approach of <tt>TObjString</tt>-type configuration objects allows to treat
+ * configuration from both @ref DoInit and @ref Reconfigure in the same way.
+ *
+ * The base class provides the function ConfigureFromArgumentString() which loops over
+ * all arguments and calls the child's method ScanConfigurationArgument(). Here the
+ * actual treatment of the argument and its parameters needs to be implemented.
+ * ConfigureFromArgumentString() can treat both arrays of arguments and arguments in
+ * one single string separated by blanks. The two options can be mixed.
+ *
+ * A second bas class function ConfigureFromCDBTObjString() allows to configure
+ * directly from a number of OCDB objects. This requires the entries to be of
+ * type TObjString and the child implementation of ScanConfigurationArgument().
+ *
* @section alihltcomponent-handling Component handling
* The handling of HLT analysis components is carried out by the AliHLTComponentHandler.
* Component are registered automatically at load-time of the component shared library
* under the following suppositions:
* - the component library has to be loaded from the AliHLTComponentHandler using the
* @ref AliHLTComponentHandler::LoadLibrary method.
+ * - the library defines an AliHLTModuleAgent which registers all components.
+ * See AliHLTModuleAgent::RegisterComponents <br>
+ * or <br>
* - the component implementation defines one global object (which is generated
- * when the library is loaded)
+ * when the library is loaded) <br>
*
* @subsection alihltcomponent-design-rules General design considerations
* The analysis code should be implemented in one or more destict class(es). A
*
* Further rules:
* - avoid big static arrays in the component, allocate the memory at runtime
+ * - allocate all kind of complex data members (like classes, ROOT TObjects of
+ * any kind) dynamically in DoInit and clean up in DoDeinit
+ *
+ * @section alihlt_component_arguments Default arguments
+ * The component base class provides some default arguments:
+ * <!-- NOTE: ignore the \li. <i> and </i>: it's just doxygen formatting -->
+ * \li -loglevel=level <br>
+ * \li -object-compression=level <br>
+ * compression level for ROOT objects, default is defined by
+ * @ref ALIHLTCOMPONENT_DEFAULT_OBJECT_COMPRESSION
+ * \li -pushback-period=period <br>
+ * scale down for PushBack of objects, shipped only for one event
+ * every <i>period</i> seconds
*
* @ingroup alihlt_component
* @section alihltcomponent-members Class members
/**
* Init function to prepare data processing.
* Initialization of common data structures for a sequence of events.
- * The call is redirected to the internal method @ref DoInit which can be
- * overridden by the child class.<br>
+ * The call is redirected to the internal method DoInit which can be
+ * overridden by the child class.
* During Init also the environment structure is passed to the component.
- * @param environ environment pointer with environment dependend function
+ * @param comenv environment pointer with environment dependent function
* calls
- * @param environParam additionel parameter for function calls, the pointer
+ * @param environParam additional parameter for function calls, the pointer
* is passed as it is
* @param argc size of the argument array
- * @param argv agument array for component initialization
+ * @param argv augment array for component initialization
*/
- virtual int Init( const AliHLTAnalysisEnvironment* environ, void* environParam, int argc, const char** argv );
+ virtual int Init( const AliHLTAnalysisEnvironment* comenv, void* environParam, int argc, const char** argv );
/**
* Clean-up function to terminate data processing.
*/
int SetComponentDescription(const char* desc);
+ /**
+ * Set the running environment for the component.
+ * Originally, the environment was set in the Init function. However, the setup of
+ * the CDB is required before. In order to have proper logging functionality, the
+ * environment is required.
+ * @param comenv environment pointer with environment dependent function
+ * calls
+ * @param environParam additional parameter for function calls, the pointer
+ * is passed as it is
+ */
+ int SetComponentEnvironment(const AliHLTAnalysisEnvironment* comenv, void* environParam);
+
// Information member functions for registration.
/**
virtual int GetOutputDataTypes(AliHLTComponentDataTypeList& tgtList);
/**
- * Get a ratio by how much the data volume is shrinked or enhanced.
+ * Get a ratio by how much the data volume is shrunken or enhanced.
* The function is pure virtual and must be implemented by the child class.
* @param constBase <i>return</i>: additive part, independent of the
* input data volume
*/
int SetStopwatches(TObjArray* pStopwatches);
+ /**
+ * Customized logging function.
+ * The chain id, component id and pointer is added at the beginning of each message.
+ */
+ int LoggingVarargs(AliHLTComponentLogSeverity severity,
+ const char* originClass, const char* originFunc,
+ const char* file, int line, ... ) const;
+
+ /**
+ * Get size of last serialized object.
+ * During PushBack, TObjects are serialized in a separate buffer. The
+ * size of the last object can be retrieved by this function.
+ *
+ * This might be especially useful for PushBack failures caused by too
+ * small output buffer.
+ */
+ int GetLastObjectSize() const {return fLastObjectSize;}
+
protected:
/**
* part of a normal event, the component configuration is called first.
*
* The CDB path parameter specifies the path in the CDB, i.e. without
- * leading absolute path of the CDB location. The framework might alse
+ * leading absolute path of the CDB location. The framework might also
* provide the id of the component in the analysis chain.
*
+ * The actual sequence of configuration depends on the component. As a
+ * general rule, the component should load the specific OCDB object if
+ * provided as parameter, and load the default objects if the parameter
+ * is NULL. However, other schemes are possible. See @ref
+ *
* \b Note: The CDB will be initialized by the framework, either already set
* from AliRoot or from the wrapper interface during initialization.
*
*/
virtual int ReadPreprocessorValues(const char* modules);
+ /**
+ * Child implementation to scan a number of configuration arguments.
+ * The method is invoked by the framework in conjunction with the
+ * common framework functions ConfigureFromArgumentString and
+ * ConfigureFromCDBTObjString.
+ * Function needs to scan the argument and optional additional
+ * parameters and returns the number of elements in the array which
+ * have been treated.
+ * @param argc
+ * @param argv
+ * @return number of arguments which have been scanned or neg error
+ * code if failed <br>
+ * \li -EINVAL unknown argument
+ * \li -EPROTO protocol error, e.g. missing parameter
+ */
+ virtual int ScanConfigurationArgument(int argc, const char** argv);
+
/**
* Custom handler for the SOR event.
* Is invoked from the base class if an SOR event is in the block list.
* The handler is called before the processing function. The processing
* function is skipped if there are no other data blocks available.
*
- * See StartOfRun() for mor ecomments of the sequence of steering events.
+ * See StartOfRun() for more comments of the sequence of steering events.
*
* @return neg. error code if failed
*/
*/
int GetEventDoneData( unsigned long size, AliHLTComponentEventDoneData** edd );
+ /**
+ * Allocate an EventDoneData structure for the current event .
+ * The method allocates the memory internally and does not interact with the current Framework.
+ * The allocated data structure is empty initially and can be filled by calls to the
+ * @ref PushEventDoneData method. The memory will be automatically released after the event has been processed.
+ *
+ */
+ int ReserveEventDoneData( unsigned long size );
+
+ /**
+ * Push a 32 bit word of data into event done data for the current event which
+ * has previously been allocated by the @ref ReserveEventDoneData method.
+ */
+ int PushEventDoneData( AliHLTUInt32_t eddDataWord );
+
+ /**
+ * Release event done data previously reserved by @ref ReserveEventDoneData
+ */
+ void ReleaseEventDoneData();
+
+ /**
+ * Get the pointer to the event done data available/built so far for the current event via
+ * @ref ReserveEventDoneData and @ref PushEventDoneData
+ */
+ AliHLTComponentEventDoneData* GetCurrentEventDoneData()
+ {
+ return fEventDoneData;
+ }
+
/**
* Helper function to convert the data type to a string.
*/
void DataType2Text(const AliHLTComponentDataType& type, char output[kAliHLTComponentDataTypefIDsize+kAliHLTComponentDataTypefOriginSize+2]) const;
+ /**
+ * Loop through a list of component arguments.
+ * The list can be either an array of separated strings or one single
+ * string containing blank separated arguments, or both mixed.
+ * ScanConfigurationArgument() is called to allow the component to treat
+ * the individual arguments.
+ * @return neg. error code if failed
+ */
+ int ConfigureFromArgumentString(int argc, const char** argv);
+
+ /**
+ * Read configuration objects from OCDB and configure from
+ * the content of TObjString entries.
+ * @param entries blank separated list of OCDB paths
+ * @return neg. error code if failed
+ */
+ int ConfigureFromCDBTObjString(const char* entries);
+
+ /**
+ * Load specified entry from the OCDB and extract the object.
+ * The entry is explicitely unloaded from the cache before it is loaded.
+ * @param path path of the entry under to root of the OCDB
+ * @param version version of the entry
+ * @param subVersion subversion of the entry
+ */
+ TObject* LoadAndExtractOCDBObject(const char* path, int version = -1, int subVersion = -1);
+
+
/**
* Get event number.
* @return value of the internal event counter
*/
int GetNumberOfInputBlocks() const;
+ /**
+ * Get id of the current event
+ * @return event id
+ */
+ AliHLTEventID_t GetEventId() const;
+
/**
* Get the first object of a specific data type from the input data.
- * The hight-level methods provide functionality to transfer ROOT data
+ * The High-level methods provide functionality to transfer ROOT data
* structures which inherit from TObject.
*
* The method looks for the first ROOT object of type dt in the input stream.
* If also the class name is provided, the object is checked for the right
* class type. The input data block needs a certain structure, namely the
* buffer size as first word. If the cross check fails, the retrieval is
- * silently abondoned, unless the \em bForce parameter is set.<br>
+ * silently abandoned, unless the \em bForce parameter is set.<br>
* \b Note: THE OBJECT MUST NOT BE DELETED by the caller.
*
* If called without parameters, the function tries to create objects from
/**
* Get the first object of a specific data type from the input data.
- * The hight-level methods provide functionality to transfer ROOT data
+ * The High-level methods provide functionality to transfer ROOT data
* structures which inherit from TObject.
* The method looks for the first ROOT object of type specified by the ID and
* Origin strings in the input stream.
* If also the class name is provided, the object is checked for the right
* class type. The input data block needs a certain structure, namely the
* buffer size as first word. If the cross check fails, the retrieval is
- * silently abondoned, unless the \em bForce parameter is set.<br>
+ * silently abandoned, unless the \em bForce parameter is set.<br>
* \em Note: THE OBJECT MUST NOT BE DELETED by the caller.
* @param dtID data type ID of the object
* @param dtOrigin data type origin of the object
/**
* Get the next object of a specific data type from the input data.
- * The hight-level methods provide functionality to transfer ROOT data
+ * The High-level methods provide functionality to transfer ROOT data
* structures which inherit from TObject.
* The method looks for the next ROOT object of type and class specified
* to the previous @ref GetFirstInputObject call.<br>
/**
* Get data specification of an input block.
- * Get data specification of the input bblock previously fetched via
+ * Get data specification of the input block previously fetched via
* GetFirstInputObject/NextInputObject or the last one if no block
* specified.
* @param pBlock pointer to input block
* @return data specification, kAliHLTVoidDataSpec if failed
*/
- AliHLTUInt32_t GetSpecification(const AliHLTComponentBlockData* pBlock=NULL);
+ AliHLTUInt32_t GetSpecification(const AliHLTComponentBlockData* pBlock);
/**
* Forward an input object to the output.
* Insert an object into the output.
* If header is specified, it will be inserted before the root object,
* default is no header.
+ * The publishing can be downscaled by means of the -pushback-period
+ * parameter. This is especially useful for histograms which do not
+ * need to be sent for every event.
* @param pObject pointer to root object
* @param dt data type of the object
* @param spec data specification
* Insert an object into the output.
* If header is specified, it will be inserted before the root object,
* default is no header.
+ * The publishing can be downscaled by means of the -pushback-period
+ * parameter. This is especially useful for histograms which do not
+ * need to be sent for every event.
* @param pObject pointer to root object
* @param dtID data type ID of the object
* @param dtOrigin data type origin of the object
*/
const char* GetChainId() const {return fChainId.c_str();}
+ /**
+ * Get a timestamp of the current event
+ * Exact format needs to be documented.
+ */
+ AliHLTUInt32_t GetTimeStamp() const;
+
+ /**
+ * Get the period number.
+ * Upper 28 bits (36 to 63) of the 64-bit event id
+ */
+ AliHLTUInt32_t GetPeriodNumber() const;
+
+ /**
+ * Get the period number.
+ * 24 bits, 12 to 35 of the 64-bit event id
+ */
+ AliHLTUInt32_t GetOrbitNumber() const;
+
+ /**
+ * Get the bunch crossing number.
+ * 12 bits, 0 to 12 of the 64-bit event id
+ */
+ AliHLTUInt16_t GetBunchCrossNumber() const;
+
+ /**
+ * Setup the CTP accounting functionality of the base class.
+ * The method can be invoked from DoInit() for componenets which want to
+ * use the CTP functionality of the base class.
+ *
+ * The AliHLTCTPData is initialized with the trigger classes from the ECS
+ * parameters. The base class automatically increments the counters according
+ * to the trigger pattern in the CDH before the event processing.
+ */
+ int SetupCTPData();
+
+ /**
+ * Get the instance of the CTP data.
+ */
+ const AliHLTCTPData* CTPData() const {return fpCTPData;}
+
+ /**
+ * Check whether a combination of trigger classes is fired.
+ * The expression can contain trigger class ids and logic operators
+ * like &&, ||, !, and ^, and may be grouped by parentheses.
+ * @param expression a logic expression of trigger class ids
+ * @param trigData the trigger data data
+ */
+ bool EvaluateCTPTriggerClass(const char* expression, AliHLTComponentTriggerData& trigData) const;
+
+ /**
+ * Get the overall solenoid field.
+ */
+ Double_t GetBz();
+ /**
+ * Get the solenoid field at point r.
+ */
+ Double_t GetBz(const Double_t *r);
+ /**
+ * Get the solenoid field components at point r.
+ */
+ void GetBxByBz(const Double_t r[3], Double_t b[3]);
+
/**
* Check whether the current event is a valid data event.
* @param pTgt optional pointer to get the event type
AliHLTUInt32_t offset,
const vector<AliHLTUInt32_t>& parents) const;
+ /**
+ * Scan the ECS parameter string.
+ * The framework provides both the parameters of CONFIGURE and ENGAGE
+ * in one string in a special data block kAliHLTDataTypeECSParam
+ * {ECSPARAM:PRIV}. The general format is
+ * <command>;<parameterkey>=<parametervalue>;<parameterkey>=<parametervalue>;...
+ */
+ int ScanECSParam(const char* ecsParam);
+
+ /**
+ * The trigger classes are determined from the trigger and propagated by
+ * ECS as part of the ENGAGE command parameter which is sent through the
+ * framework during the SOR event. This function treats the value of the
+ * parameter key CTP_TRIGGER_CLASS.
+ */
+ int InitCTPTriggerClasses(const char* ctpString);
+
+ enum {
+ kRequireSteeringBlocks = 0x1,
+ kDisableComponentStat = 0x2
+ };
+
/** The global component handler instance */
static AliHLTComponentHandler* fgpComponentHandler; //! transient
AliHLTEventDDL* fpDDLList; //! transient
/** external fct to set CDB run no, indicates external CDB initialization */
- void* fCDBSetRunNoFunc; //! transient
+ void (*fCDBSetRunNoFunc)(); //! transient
/** id of the component in the analysis chain */
string fChainId; //! transient
/** optional benchmarking for the component statistics */
TStopwatch* fpBenchmark; //! transient
- /** component requires steering data blocks */
- bool fRequireSteeringBlocks; //! transient
+ /** component flags, cleared in Deinit */
+ AliHLTUInt32_t fFlags; //! transient
/** current event type */
AliHLTUInt32_t fEventType; //! transient
/** component arguments */
string fComponentArgs; //! transient
- ClassDef(AliHLTComponent, 8)
+
+ /** event done data */
+ AliHLTComponentEventDoneData* fEventDoneData; //! transient
+
+ /** Reserved size of the memory stored at fEventDoneData */
+ unsigned long fEventDoneDataSize; //! transient
+
+ /** Comression level for ROOT objects */
+ int fCompressionLevel; //! transient
+
+ /** size of last PushBack-serialized object */
+ int fLastObjectSize; //! transient
+
+ /** array of trigger class descriptors */
+ AliHLTCTPData* fpCTPData; //! transient
+
+ /// update period for PushBack calls
+ int fPushbackPeriod; //! transient
+ /// time of last executed PushBack
+ int fLastPushBackTime; //! transient
+
+ ClassDef(AliHLTComponent, 14)
};
#endif