MCTruthTestWorkflow.cxx File Reference

#include <boost/program_options.hpp>
#include "Framework/WorkflowSpec.h"
#include "Framework/ConfigParamSpec.h"
#include "Framework/CompletionPolicy.h"
#include "Framework/CompletionPolicyHelpers.h"
#include "Framework/DeviceSpec.h"
#include "MCTruthSourceSpec.h"
#include "MCTruthWriterSpec.h"
#include "MCTruthReaderSpec.h"
#include "Framework/runDataProcessing.h"

Go to the source code of this file.

Functions
void	customize (std::vector< o2::framework::ConfigParamSpec > &workflowOptions)
WorkflowSpec	defineDataProcessing (ConfigContext const &configcontext)
	This function hooks up the the workflow specifications into the DPL driver.

Function Documentation

customize()

void customize

(

std::vector< o2::framework::ConfigParamSpec > &

workflowOptions

)

Definition at line 25 of file MCTruthTestWorkflow.cxx.

defineDataProcessing()

WorkflowSpec defineDataProcessing

(

ConfigContext const &

configcontext

)

This function hooks up the the workflow specifications into the DPL driver.

This function is required to be implemented to define the workflow specifications

We define at run time the number of devices to be attached to the workflow and the input matching string of the device. This is is done with a configuration string like the following one, where the input matching for each device is provide in comma-separated strings. For instance

A:TOF/RAWDATA/768;B:TOF/RAWDATA/1024,C:TOF/RAWDATA/1280;D:TOF/RAWDATA/1536

will lead to a workflow with 2 devices which will input match

tof-compressor-0 --> A:TOF/RAWDATA/768;B:TOF/RAWDATA/1024 tof-compressor-1 --> C:TOF/RAWDATA/1280;D:TOF/RAWDATA/1536

This gets a table handle from the message.

From the handle, we construct the actual arrow table which is then used as a source for the RDataFrame. This is probably easy to change to a:

auto rdf = ctx.inputs().get<RDataSource>("xz");

Get the input from the converter.

Get a table builder to build the results

Definition at line 36 of file MCTruthTestWorkflow.cxx.