actions
Loading...
Searching...
No Matches
GRun Class Reference

Thread-local run object created for each Geant4 run. More...

#include <gRun.h>

Public Member Functions

 GRun (std::shared_ptr< GOptions > gopts, std::shared_ptr< gdynamicdigitization::dRoutinesMap > digi_map)
 Constructs the run object for the current thread.
 
- Public Member Functions inherited from GBase< GRun >
 GBase (const std::shared_ptr< GOptions > &gopt, std::string logger_name="")
 
 GBase (const std::shared_ptr< GLogger > &logger)
 
 GBase (const GBase &)=default
 
 GBase (GBase &&) noexcept=default
 
virtual ~GBase ()
 
GBaseoperator= (const GBase &)=default
 
GBaseoperator= (GBase &&) noexcept=default
 

Additional Inherited Members

- Protected Attributes inherited from GBase< GRun >
std::shared_ptr< GLoggerlog
 

Detailed Description

In Geant4, a run is a sequence of events started by the run manager BeamOn(). In multithreaded mode, each worker thread creates its own run object; Geant4 may later merge worker runs into a global run.

GEMC uses this run object as the place where run-level services can be attached. In particular, the digitization routines map is stored so that event-level logic can reference consistent digitization behavior for the lifetime of the run.

Creation:

  • Instances are created by the run action via GRunAction::GenerateRun().

Definition at line 53 of file gRun.h.

Constructor & Destructor Documentation

◆ GRun()

GRun::GRun ( std::shared_ptr< GOptions > gopts,
std::shared_ptr< gdynamicdigitization::dRoutinesMap > digi_map )
Parameters
goptsShared configuration used by this run for logging and run-level behavior.
digi_mapShared digitization routines map used throughout the run.

Definition at line 9 of file gRun.cc.


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