Project
Loading...
Searching...
No Matches
o2aod_mc_to_hepmc.cxx File Reference

Go to the source code of this file.

Classes

struct  AodToHepmc
 

Typedefs

using WorkflowSpec = o2::framework::WorkflowSpec
 
using DataProcessorSpec = o2::framework::DataProcessorSpec
 
using ConfigContext = o2::framework::ConfigContext
 

Functions

WorkflowSpec defineDataProcessing (ConfigContext const &cfg)
 This function hooks up the the workflow specifications into the DPL driver.
 

Typedef Documentation

◆ ConfigContext

◆ DataProcessorSpec

◆ WorkflowSpec

Function Documentation

◆ defineDataProcessing()

WorkflowSpec defineDataProcessing ( ConfigContext const &  cfg)

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

Entry point of o2-sim-mcevent-to-hepmc

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 182 of file o2aod_mc_to_hepmc.cxx.