+ * TObjects can also be used for the trigger algorithm. In such cases a symbol
+ * needs to be defined in the global trigger menu which can then be used inside
+ * the trigger condition expressions.
+ *
+ * <h2>General properties:</h2>
+ *
+ * Component ID: \b HLTGlobalTrigger <br>
+ * Library: \b libAliHLTTrigger.so <br>
+ * Input Data Types: ::kAliHLTAnyDataType <br>
+ * Output Data Types: kAliHLTDataTypeGlobalTrigger and kAliHLTDataTypeReadoutList <br>
+ *
+ * <h2>Mandatory arguments:</h2>
+ * None.
+ *
+ * <h2>Optional arguments:</h2>
+ * <!-- NOTE: ignore the \li. <i> and </i>: it's just doxygen formatting -->
+ * \li -config <i>filename</i> <br>
+ * Indicates the configuration macro file to use for the global HLT trigger menu.
+ * \li -includepath <i>path</i> <br>
+ * Indicates the include path to use if the automatically generated code that
+ * implements the global HLT trigger requires non-standard includes.
+ * \li -include <i>filename</i> <br>
+ * Indicates a file name that should be included in the automatically generated
+ * trigger implementation code.
+ * \li -debug <br>
+ * If specified the automatically generated class will contain extra debugging
+ * code and the ACLiC system will have debugging compilation turned on.
+ * \li -cint <br>
+ * Use CINT to interprete the generated global trigger instead of compiling it.
+ * This will also be the case if no compiler is available.
+ * \li -usecode <i>filename</i> <i>classname</i> <br>
+ * Used to force the component to use an existing class for the global HLT trigger
+ * class implementation, with the name of <i>classname</i> and found in the file
+ * <i>filename</i>.
+ * \li -skipctp <br>
+ * Indicates that the CTP data should not be added to the global HLT trigger decision.
+ * \li -forward-input <br>
+ * Forward the input objects instead of adding them to the global HLT trigger decision.
+ * This will also add a short info on the input objects and decisions, like
+ * -include-input=short, to switch off -include-input=none can be placed after the
+ * parameter
+ * \li -include-input[=none,short,objects,both] <br>
+ * Steer adding of input objects to the global HLT trigger decision.
+ * Options: none - include nothing, short - include a short TNames array,
+ * objects - include objects, by default on
+ * both - include both objects and short info
+ * \li -process-all-events <br>
+ * Indicates that all events should be processed with the global trigger logic and
+ * not just the data events. The default is not to process just the data events.
+ * \li -monitoring[=n] <br>
+ * enable monitoring trigger once every n seconds, enable for every event if
+ * parameter n is omitted
+ * \li -dont-make-software-triggers <br>
+ * This option prevents the Common Data Header from being interpreted to generate
+ * software event input triggers for the trigger menu. Normally the following default
+ * triggers are available in the trigger menu:
+ * START_OF_DATA - start of data event.
+ * END_OF_DATA - end of data event.
+ * SOFTWARE - general software trigger.
+ * CALIBRATION - calibration trigger.
+ * With this option these will not be automatically generated by the global trigger.
+ * \li -randomseed <i>number</i> <br>
+ * Specifies the random number seed to give to the internal random number generator.
+ * This is only useful for debugging to generate reproducible number sequences.
+ * The random numbers are only used if a trigger is scaled down using the scale down
+ * option in a trigger menu item. The seed is normally randomly chosen by default.
+ *
+ * <h2>Configuration:</h2>
+ * Configured from CDB but can be overridden with the -config argument.
+ *
+ * <h2>Default CDB entries:</h2>
+ * HLT/ConfigHLT/HLTGlobalTrigger - Contains the global trigger menu.
+ *
+ * <h2>Performance:</h2>
+ * This is a linear function of the number of input triggers (AliHLTTrigger) that
+ * need to be processed.
+ * For a modest trigger menu configurations the processing time per event should
+ * be on the order of a few milliseconds.
+ *
+ * <h2>Memory consumption:</h2>
+ * Memory consumption is minimal. It should be on the order of 2 or 3 MBytes.
+ *
+ * <h2>Output size:</h2>
+ * This will depend almost linearly on the number of intput triggers and summary
+ * data objects used. Thus, for every trigger (AliHLTTrigger object) specified
+ * in the trigger menu the output size will require about 1 kBytes.
+ * Then for every summary data object (i.e. TObject symbol defined in the trigger
+ * menu configuration) one will need an extra few kBytes, depending on the size
+ * of the summary objects.
+ * In total one would expect no more than a MByte output size for a large trigger
+ * configuration and typically only a few kBytes for a small or optimised one.
+ *
+ * \ingroup alihlt_trigger_components