![]() |
Project
|
This is an executable that reads a data file from disk and sends the individual CRU pages via DPL. More...
#include <random>
#include <iostream>
#include <queue>
#include <fstream>
#include <stdexcept>
#include "Framework/CallbackService.h"
#include "Framework/ConfigParamRegistry.h"
#include "Framework/ControlService.h"
#include "Framework/DataProcessorSpec.h"
#include "Framework/Lifetime.h"
#include "Framework/Output.h"
#include "Framework/Task.h"
#include "Framework/WorkflowSpec.h"
#include "DPLUtils/DPLRawParser.h"
#include "Headers/RAWDataHeader.h"
#include "DetectorsRaw/RDHUtils.h"
#include "DetectorsRaw/HBFUtils.h"
#include "CommonDataFormat/TFIDInfo.h"
#include "Framework/runDataProcessing.h"
Go to the source code of this file.
Classes | |
struct | o2::mch::raw::TimeFrame |
class | o2::mch::raw::FileReaderTask |
Namespaces | |
namespace | o2 |
a couple of static helper functions to create timestamp values for CCDB queries or override obsolete objects | |
namespace | o2::mch |
namespace | o2::mch::raw |
Typedefs | |
using | o2::mch::raw::TFQueue = std::queue< TimeFrame > |
Functions | |
o2::framework::DataProcessorSpec | o2::mch::raw::getFileReaderSpec (const char *specName) |
void | customize (std::vector< ConfigParamSpec > &workflowOptions) |
WorkflowSpec | defineDataProcessing (const ConfigContext &cfgc) |
Variables | |
TFQueue | o2::mch::raw::tfQueues [NFEEID][NLINKS] |
This is an executable that reads a data file from disk and sends the individual CRU pages via DPL.
This is an executable that reads a data file from disk and sends the individual CRU pages via the Data Processing Layer. It can be used as a data source for O2 development. For example, one can do:
Definition in file cru-page-reader-workflow.cxx.
void customize | ( | std::vector< ConfigParamSpec > & | workflowOptions | ) |
Definition at line 652 of file cru-page-reader-workflow.cxx.
WorkflowSpec defineDataProcessing | ( | const ConfigContext & | cfgc | ) |
To be implemented by the user to specify one or more DataProcessorSpec.
Use the ConfigContext context in input to get the value of global configuration properties like command line options, number of available CPUs or whatever can affect the creation of the actual workflow.
The workflow executable for the stand alone CPV reconstruction workflow The basic workflow for CPV reconstruction is defined in RecoWorkflow.cxx and contains the following default processors
The default workflow can be customized by specifying input and output types e.g. digits, raw, tracks.
MC info is processed by default, disabled by using command line option --disable-mc
This function hooks up the the workflow specifications into the DPL driver.
The workflow executable for the stand alone CTP reconstruction workflow
The workflow executable for the stand alone EMCAL reconstruction workflow The basic workflow for EMCAL reconstruction is defined in RecoWorkflow.cxx and contains the following default processors
The default workflow can be customized by specifying input and output types e.g. digits, raw, tracks.
MC info is processed by default, disabled by using command line option --disable-mc
This function hooks up the the workflow specifications into the DPL driver.
The workflow executable for the stand alone TOF reconstruction workflow The basic workflow for TOF reconstruction is defined in RecoWorkflow.cxx and contains the following default processors
The default workflow can be customized by specifying input and output types e.g. digits, raw, clusters.
MC info is processed by default, disabled by using command line option --disable-mc
This function hooks up the the workflow specifications into the DPL driver.
DPL Workflow to process MCH or MID DCS data points.
The expected input is a vector of DataPointCompositeObject containing only MCH (or only MID) data points.
Those datapoints are accumulated into DPMAPs (map from alias names to vector of DataPointValue).
The accumulated DPMAPs are sent to the output whenever :
DPL workflow which generates fake random MCH DCS data points.
Data points are generated for HV (currents and voltages) as well as for LV (DualSampa analog and digital voltages, and SOLAR voltages).
DPL workflow which generates fake random MID DCS data points.
Data points are generated for HV (currents and voltages).
Definition at line 663 of file cru-page-reader-workflow.cxx.