Introduction

The GDynamicDigitization module defines the base interface and utilities used to implement detector digitization routines as dynamically loadable plugins.

At a high level, a digitization plugin is responsible for:

defining readout timing/storage rules via defineReadoutSpecs()
optionally loading constants and a translation table via loadConstants() and loadTT()
converting a true hit into digitized output via digitizeHit()
optionally collecting a standardized “true information” payload via collectTrueInformation()

Sensitive-detector and digitization data flow

Key components

GDynamicDigitization : Abstract base class defining the plugin surface.
GTouchableModifiers : Helper container used when a digitizer needs to compute weighted/weighted-time modifiers for touchables.
GReadoutSpecs : Small immutable specification used to compute electronics time bin indices.

Configuration

gdynamicdigitization::defineOptions() defines:

recordZeroEdep: retain hits with exactly zero deposited energy.
digitization_variation: override the geometry variation used to load constants and translation tables.
applyThresholds: comma- or space-separated digitization systems that apply channel thresholds, or all.
applyInefficiencies: systems that apply per-channel efficiency rejection, or all.

It also aggregates the event-data, run-data, translation-table, and plugin-factory option sets required by the digitization workflow.

Verbosity and logging

Most classes in this module log through the project logging infrastructure. Typical meanings (by convention) are:

level 0 : essential information and high-level workflow milestones (e.g. which plugin was loaded).
level 1 : configuration details and one-time initialization information (e.g. readout specs).
level 2 : per-hit or per-event informational tracing (may be verbose for large jobs).
debug : fine-grained, developer-oriented messages intended for diagnosing behavior (often includes intermediate indices, computed values, or branch decisions).

Examples

The module ships example programs illustrating how to implement and load plugins:

Example plugin implementation

File : examples/gplugin_test_example.h, examples/gplugin_test_example.cc
Summary : Implements a minimal digitization plugin (readout specs, constants, TT, hit digitization) and exposes the required factory symbol GDynamicDigitizationFactory.

Example plugin loading and multi-threaded usage

File : examples/plugin_load_example.cc
Summary : Loads a plugin with gdynamicdigitization::dynamicRoutinesMap(), calls loadConstants(), then runs a small multi-threaded event loop that digitizes a few hits per event.

Table of Contents