assigning geant4 run number from gemc options

Author: maureeungaro

gemc/eventDispenser/eventDispenser.cc

@@ -15,6 +15,7 @@
 
 // geant4
 #include "G4UImanager.hh"
+#include "G4RunManager.hh"
 
 using namespace std;
 
@@ -180,6 +181,9 @@ int EventDispenser::processEvents() {
 		}
 
 		log->info(1, "Starting run ", runNumber, " with ", nevents, " events.");
+		// Tag the next G4Run with this run number. Guarded because standalone/unit-test
+		// contexts (e.g. the event_dispenser example) may run without a G4RunManager.
+		if (G4RunManager* g4rm = G4RunManager::GetRunManager()) { g4rm->SetRunIDCounter(runNumber); }
 
 		// Dispatch all events for this run in a single call.
 		// The command string is a standard Geant4 UI command: \c /run/beamOn <N>.

releases/0.3.md

@@ -9,6 +9,7 @@ This version includes:
 - Volume inspection from the geometry tree
 - Geometry-tree right panel redesign: sticky style buttons, expanding parameters box, system-aware visibility
 - Unified `value*unit` notation for `gparticle` kinematic fields
+- `digitization_variation` option to override the gsystem variation for digitization constants/tables
 - `GEMC_PLUGIN_PATH` and `-plugin_path` for external plugin discovery
 - Pre-parse plugin options hook for dynamic plugin option registration
 - Clearer command-line help: reviewed every module's option/switch help, added usage examples, and
@@ -501,6 +502,13 @@ Both x86_64 and ARM64 platforms are supported.
   (`gsystem`, selects the geometry/conditions variation) versus `run` (`eventDispenser`, the run number
   assigned to generated events and the key used with `-run_weights`); both descriptions and help now
   cross-reference each other and the automatic Geant4 `g4runno`.
+- Added a `digitization_variation` option (defined by the `gdynamicdigitization` module) that overrides the
+  per-system `gsystem` variation used when digitization routines load their calibration constants and
+  translation tables. When unset (the default), each routine follows the variation of the `gsystem` it
+  belongs to, resolved per digitization name at geometry load in `loadDigitizationPlugins()`; when set, the
+  override applies to every routine. The resolved variation is stored on each `GDynamicDigitization` routine
+  and passed to `loadConstants()`/`loadTT()`. This also fixes the variation reaching those calls, which
+  previously defaulted to an empty string because `EventDispenser`'s variation member was never assigned.
 - Removed the unused `checkOverlaps` switch from `g4system`: it was registered and shown in help but
   never read. Overlap checking is controlled solely by the integer `check_overlaps` option, whose
   value `1` already enables the `G4PVPlacement` surface overlap check (`pSurfChk`) at volume placement;