Rivet::AnalysisHandler Class Reference The key class for coordination of Analysis objects and the event loop. More...
Detailed DescriptionThe key class for coordination of Analysis objects and the event loop. A class which handles a number of analysis objects to be applied to generated events. An Member Enumeration Documentation◆ Stage
Indicate which Rivet stage we're in. At the moment, only INIT is used to enable booking. Member Function Documentation◆ addAnalyses()
Add analyses to the run list using their names. The actual ◆ addAnalysis()
Add an analysis to the run list using its name. The actual Analysis to be used will be obtained via AnalysisLoader::getAnalysis(string). If no matching analysis is found, no analysis is added (i.e. the null pointer is checked and discarded. ◆ analyze() [1/2]
Analyze the given event by reference. This function will call the AnalysisBase::analyze() function of all included analysis objects. ◆ analyze() [2/2]
Analyze the given event by pointer. This function will call the AnalysisBase::analyze() function of all included analysis objects, after checking the event pointer validity. ◆ beamIds()
Get beam IDs for this run, usually determined from the first event.
◆ dump()
◆ finalize()
Finalize a run. This function calls the AnalysisBase::finalize() functions of all included analysis objects. ◆ getPreload()
Get a pointer to a preloaded yoda object with the given path, or null if path is not found. ◆ mergeYodas()
Merge the vector of YODA files, using the cross-section and weight information provided in each. Each file in aofiles is assumed to have been produced by Rivet. By default the files are assumed to contain different processes (or the same processs but mutually exclusive cuts), but if equiv if true, the files are assumed to contain output of completely equivalent (but statistically independent) Rivet runs. The corresponding analyses will be loaded and their analysis objects will be filled with the merged result. finalize() will be run on each relevant analysis. The resulting YODA file can then be written out by writeData(). If delopts is non-empty, it is assumed to contain names of different options to be merged into the same analysis objects. ◆ numEvents()
Get the number of events seen. Should only really be used by external steering code or analyses in the finalize phase. N.B. This only reports the count for the last collapsed event group and hence ignores any additional sub-events seen so far. References defaultWeightIndex(). ◆ numWeights()
Indices of the weights in the original weight matrix. Are any of the weights non-numeric? ◆ readData()
Read analysis plots into the histo collection from the given stream. Use the fmt flag to specify the YODA output format (yoda, yoda.gz, yoda.h5, ...) ◆ setAODump()
Configure the AnalysisObject dump rate and destination. Tell Rivet to dump intermediate result to a file named dumpfile every period'th event. If period is not positive, no dumping will be done. References dump(). Referenced by setNoAODump(). ◆ setIgnoreBeams()
◆ sqrtS()
Get energy for this run, usually determined from the first event.
Referenced by setRunBeams(). ◆ sumW()
Access the sum of the event weights seen. This is the weighted equivalent of the number of events. It should only be used by external steering code or analyses in the finalize phase. ◆ writeData()
Write all analyses' plots (via getData) to the given stream. Use the fmt flag to specify the YODA output format (yoda, yoda.gz, yoda.h5, ...) The documentation for this class was generated from the following file:
Generated on Fri Apr 28 2023 08:48:50 for Rivet by |