the base class for EventLoop instrumentation module More...

#include <Module.h>

Inherits AsgComponent.

Collaboration diagram for EL::Detail::Module:

Public Member Functions
virtual StatusCode	firstInitialize (ModuleData &data)
	action at the the very beginning of the worker job More...

virtual StatusCode	preFileInitialize (ModuleData &data)
	action before opening the first file in the worker job More...

virtual StatusCode	onInitialize (ModuleData &data)
	action just before algorithms are initialized More...

virtual StatusCode	processInputs (ModuleData &data, IInputModuleActions &actions)
	process all input files More...

virtual StatusCode	postFirstEvent (ModuleData &data)
	action after processing first event More...

virtual StatusCode	onNewInputFile (ModuleData &data)
	actions after opening a new input file More...

virtual StatusCode	onCloseInputFile (ModuleData &data)
	actions before closing an input file More...

virtual StatusCode	postCloseInputFile (ModuleData &data)
	actions after `CloseInputFile` is called on the algorithms More...

virtual StatusCode	onFileExecute (ModuleData &data)
	actions just before `fileExecute` is called on algorithms More...

virtual StatusCode	onExecute (ModuleData &data)
	actions just before `execute` is called on algorithms More...

virtual StatusCode	onFinalize (ModuleData &data)
	actions just before algorithms are finalized More...

virtual StatusCode	postFinalize (ModuleData &data)
	actions after algorithms have been finalized More...

virtual StatusCode	onWorkerEnd (ModuleData &data)
	action at the end of the worker job More...

virtual StatusCode	postFileClose (ModuleData &data)
	action at end of the worker job More...

virtual void	reportInputFailure (ModuleData &data)
	report that we failed to open our input file More...

Detailed Description

the base class for EventLoop instrumentation module

These are internal modules for EventLoop that allow to factor out non-core functionalities into separate modules. The goal here is a separation of concern, allowing to implement these modules without having to worry about the internals of EventLoop, and conversely to allow implementing the core functionality of EventLoop without having the code interwoven with a lot auxilliary code.

@warn The module interface is not considered stable and it can change without warning from one release to the next. This interface is really meant to be completely internal and users are not meant to mess with it.

Definition at line 39 of file PhysicsAnalysis/D3PDTools/EventLoop/EventLoop/Module.h.

Member Function Documentation

◆ firstInitialize()

StatusCode EL::Detail::Module::firstInitialize ( ModuleData & data )

virtual

action at the the very beginning of the worker job

This gets called as early as possible in the worker initialization. Essentially all that should happen before this is to load all the modules. The main purpose is to start any benchmarks that are meant to capture the initialization process as well.

Reimplemented in EL::Detail::MemoryMonitorModule, EL::Detail::AlgorithmMemoryModule, EL::Detail::AlgorithmTimerModule, and EL::Detail::StopwatchModule.

Definition at line 25 of file Module.cxx.

     {
       return ::StatusCode::SUCCESS;
     }

◆ onCloseInputFile()

StatusCode EL::Detail::Module::onCloseInputFile ( ModuleData & data )

virtual

actions before closing an input file

Reimplemented in EL::Detail::AlgorithmStateModule, and EL::Detail::TreeCacheModule.

Definition at line 43 of file Module.cxx.

     {
       return ::StatusCode::SUCCESS;
     }

◆ onExecute()

StatusCode EL::Detail::Module::onExecute ( ModuleData & data )

virtual

actions just before execute is called on algorithms

For now that is mostly used to point input modules to the right event

Reimplemented in EL::Detail::TEventModule, EL::Detail::AlgorithmStateModule, EL::Detail::MemoryMonitorModule, and EL::Detail::GridReportingModule.

Definition at line 71 of file Module.cxx.

     {
       return ::StatusCode::SUCCESS;
     }

◆ onFileExecute()

StatusCode EL::Detail::Module::onFileExecute ( ModuleData & data )

virtual

actions just before fileExecute is called on algorithms

Reimplemented in EL::Detail::AlgorithmStateModule, EL::Detail::FileExecutedModule, and EL::Detail::StopwatchModule.

Definition at line 65 of file Module.cxx.

     {
       return ::StatusCode::SUCCESS;
     }

◆ onFinalize()

StatusCode EL::Detail::Module::onFinalize ( ModuleData & data )

virtual

actions just before algorithms are finalized

Reimplemented in EL::Detail::AlgorithmStateModule, and EL::Detail::MemoryMonitorModule.

Definition at line 89 of file Module.cxx.

     {
       return ::StatusCode::SUCCESS;
     }

◆ onInitialize()

StatusCode EL::Detail::Module::onInitialize ( ModuleData & data )

virtual

action just before algorithms are initialized

This is typically used for any setup that this module needs to do.

Reimplemented in EL::Detail::TEventModule, EL::Detail::AlgorithmStateModule, EL::Detail::MemoryMonitorModule, EL::Detail::FileExecutedModule, EL::Detail::FactoryPreloadModule, and EL::Detail::WorkerConfigModule.

Definition at line 77 of file Module.cxx.

     {
       return ::StatusCode::SUCCESS;
     }

◆ onNewInputFile()

StatusCode EL::Detail::Module::onNewInputFile ( ModuleData & data )

virtual

actions after opening a new input file

Reimplemented in EL::Detail::TEventModule, EL::Detail::AlgorithmStateModule, EL::Detail::GridReportingModule, and EL::Detail::TreeCacheModule.

Definition at line 37 of file Module.cxx.

     {
       return ::StatusCode::SUCCESS;
     }

◆ onWorkerEnd()

StatusCode EL::Detail::Module::onWorkerEnd ( ModuleData & data )

virtual

action at the end of the worker job

This is mostly meant/used to print job summary statements at the very end of worker job, and actually have them show up at or at least near the end of any log file.

Reimplemented in EL::Detail::MemoryMonitorModule, EL::Detail::StopwatchModule, and EL::Detail::LeakCheckModule.

Definition at line 101 of file Module.cxx.

     {
       return ::StatusCode::SUCCESS;
     }

◆ postCloseInputFile()

StatusCode EL::Detail::Module::postCloseInputFile ( ModuleData & data )

virtual

actions after CloseInputFile is called on the algorithms

Right now that is only used to disconnect the TEvent object from the input file.

Reimplemented in EL::Detail::TEventModule.

Definition at line 49 of file Module.cxx.

     {
       return ::StatusCode::SUCCESS;
     }

◆ postFileClose()

StatusCode EL::Detail::Module::postFileClose ( ModuleData & data )

virtual

action at end of the worker job

Executed just right before worker exit successfully at this stage all outputs have been created

Reimplemented in EL::Detail::GridReportingModule, and EL::Detail::PostClosedOutputsModule.

Definition at line 107 of file Module.cxx.

     {
       return ::StatusCode::SUCCESS;
     }

◆ postFinalize()

StatusCode EL::Detail::Module::postFinalize ( ModuleData & data )

virtual

actions after algorithms have been finalized

This is usually used to calculate some job summary information that is to be stored it in the histogram output file.

Reimplemented in EL::Detail::TEventModule, EL::Detail::FileExecutedModule, EL::Detail::LeakCheckModule, EL::Detail::StopwatchModule, and EL::Detail::EventCountModule.

Definition at line 95 of file Module.cxx.

     {
       return ::StatusCode::SUCCESS;
     }

◆ postFirstEvent()

StatusCode EL::Detail::Module::postFirstEvent ( ModuleData & data )

virtual

action after processing first event

This is mostly meant to set up benchmarks that record per-event performance. While a lot of initialization happens during initialize() there is a fair amount of initialization that happens on the first event, so when recording per-event performance the first event is sort of "special" and may need to be omitted.

Reimplemented in EL::Detail::MemoryMonitorModule, and EL::Detail::LeakCheckModule.

Definition at line 55 of file Module.cxx.

     {
       return ::StatusCode::SUCCESS;
     }

◆ preFileInitialize()

StatusCode EL::Detail::Module::preFileInitialize ( ModuleData & data )

virtual

action before opening the first file in the worker job

This is mostly meant to allow loading the dictionaries before any files and associated information is loaded.

Definition at line 31 of file Module.cxx.

     {
       return ::StatusCode::SUCCESS;
     }

◆ processInputs()

StatusCode EL::Detail::Module::processInputs	(	ModuleData &	data,
		IInputModuleActions &	actions
	)

virtual

process all input files

This deviates slightly from the usual pattern for module functions in that I pass in the possible actions as an argument. See IInputModuleActions for details.

Reimplemented in EL::Detail::BatchInputModule, and EL::Detail::DirectInputModule.

Definition at line 83 of file Module.cxx.

     {
       return ::StatusCode::SUCCESS;
     }

◆ reportInputFailure()

void EL::Detail::Module::reportInputFailure ( ModuleData & data )

virtual

report that we failed to open our input file

Reimplemented in EL::Detail::GridReportingModule.

Definition at line 61 of file Module.cxx.

63 {}

The documentation for this class was generated from the following files:

Public Member Functions

Detailed Description

Member Function Documentation

◆ firstInitialize()

◆ onCloseInputFile()

◆ onExecute()

◆ onFileExecute()

◆ onFinalize()

◆ onInitialize()

◆ onNewInputFile()

◆ onWorkerEnd()

◆ postCloseInputFile()

◆ postFileClose()

◆ postFinalize()

◆ postFirstEvent()

◆ preFileInitialize()

◆ processInputs()

◆ reportInputFailure()