several changes to address geometry reload and run

Author: maureeungaro

dbselect/examples/simple_flux.py

@@ -0,0 +1,25 @@
+#!/usr/bin/env python3
+# Creates the simple_flux system used by test_reload_sequence.
+# World half-size = 150 mm so the proton gun at z = -100 mm is inside.
+from pygemc import autogeometry, GVolume
+
+cfg = autogeometry("examples", "simple_flux")
+
+gvolume = GVolume('root')
+gvolume.description = 'World'
+gvolume.make_box(150.0, 150.0, 150.0)
+gvolume.material = 'G4_AIR'
+gvolume.color = 'ghostwhite'
+gvolume.style = 0
+gvolume.publish(cfg)
+
+gvolume = GVolume('FluxPlane')
+gvolume.mother = 'root'
+gvolume.description = 'Flux Scoring Plane'
+gvolume.make_box(120.0, 120.0, 0.5)
+gvolume.material = 'G4_AIR'
+gvolume.color = 'FAFAD2'
+gvolume.set_position(0, 0, 50)
+gvolume.digitization = 'flux'
+gvolume.set_identifier('flux_plane', 1)
+gvolume.publish(cfg)

releases/0.3.md

@@ -23,10 +23,60 @@ This version includes:
   startup splash to remain visible briefly before closing.
 - Fixed setup-tab geometry reloads so the Volumes tab is rebuilt from the
   reloaded detector geometry.
-- Suppressed empty-scene Geant4 visualization warnings when starting `gemc -gui`
-  without a selected system.
+- Reopened the Geant4 GUI scene during setup-tab reloads so reloaded geometry is
+  displayed before running events.
+- Rebuilt setup-tab geometry immediately for display/Volumes updates, then
+  reinitialized through Geant4 before Run so MT workers use a fresh world.
+- Synchronized setup-tab system selection back into runtime options so pressing
+  Run after Reload uses the same geometry shown in the display.
+- Deferred Geant4 initialization when starting `gemc -gui` without a selected
+  system, preventing synthetic ROOT-world visualization state before setup-tab
+  reloads.
+- Fixed GUI Geant4 output splitting by normalizing line endings before board
+  logging instead of using a newline regular expression.
+- Allowed `gemc -gui` to open with an empty setup tab when the default
+  `gemc.db` is not present, instead of exiting with SQLite error code 209.
+- Allowed the Volumes tab to start empty when no Geant4 world has been built,
+  avoiding a fatal pre-window geometry-map lookup.
+- Generated the installed examples SQLite database during `meson install` so
+  the GUI setup tab is populated after a normal install.
+- Initialized the Geant4 run manager during the GUI pre-run geometry handoff so
+  `BeamOn` is not ignored after setup-tab reloads.
+- Rebuilt setup-tab run geometry from fresh system descriptors so preview
+  reloads do not leave factory-populated systems that duplicate ROOT volumes at
+  `BeamOn`.
 - Isolated ROOT linkage to the ROOT gstreamer plugin so the main `gemc`
   executable can run without ROOT shared libraries.
+- Fixed GUI crash (SIGABRT in `G4ToolsSGSceneHandler::GetOrCreateNode`) when
+  reloading geometry after running events: `refreshGeometryTree` now tracks
+  whether a viewer already exists and skips `/vis/open` on subsequent reloads,
+  avoiding a second viewer creation that triggers a synchronous ToolsSG refresh
+  before the Qt widget is ready.
+- Fixed hits not recorded after GUI setup-tab reload or on the second and
+  subsequent BeamOn calls: introduced a `digiplugins_need_reload` flag in
+  `GDetectorConstruction` so `loadDigitizationPlugins()` (which clears the
+  shared digitization-routines map) runs only when geometry actually changed,
+  not on every `ConstructSDandField()` invocation during routine BeamOn
+  re-initialization.  In Geant4 task-parallel MT, `RunInitialization()` can
+  overlap with workers already in their event loop; the previous code cleared
+  the shared map while workers were between `BeginOfRunAction` (which saw the
+  map populated and opened streamers) and `EndOfEventAction` (which then found
+  the map empty), causing a fatal "no digitization routine registered" error.
+  The flag is reset to `true` by `reload_geometry()` and
+  `prepare_geometry_for_run()` so that the next `ConstructSDandField()` on the
+  master thread refreshes the map exactly once per geometry change.
+- Fixed crash ("no digitization routine registered for collection X") when
+  running events after switching geometries in the GUI setup tab: Geant4's
+  `G4SDManager` accumulates sensitive detectors across geometry reloads and
+  fires `Initialize()` on all of them at the start of every event, even those
+  no longer attached to any volume in the current geometry.  These stale
+  detectors create empty hit collections that appear in `G4HCofThisEvent`.
+  `EndOfEventAction` now skips any collection whose SD name is not in the
+  current digitization-routines map with a non-fatal warning instead of
+  terminating the process, so current-geometry hits are still processed
+  correctly.
+- Cleared the digitization-routines map at the start of `loadDigitizationPlugins()` so that
+  `emplace()` cannot silently reuse stale plugin objects from a prior load.
 - Removed the need for GEMC-specific environment variables in Python example
   workflows: the API runs through the `pygemc` module, and users only need the
   executable in `PATH`.
@@ -123,8 +173,34 @@ Both x86_64 and ARM64 platforms are supported.
   0.2-second startup splash duration from `gemc.cc`.
 - Emitted a setup-view geometry reload signal and used it to recreate the GUI
   volume tree page from `GDetectorConstruction::get_g4volumes_map()`.
+- Split setup-tab reload handling into an immediate GUI preview rebuild and a
+  one-time non-propagating `G4RunManager::ReinitializeGeometry(true, false)`
+  before `BeamOn`, avoiding stale world pointers during MT worker startup.
+- Removed stale Geant4 visualization models before pre-run geometry
+  reinitialization.
+- Temporarily detached the concrete Geant4 visualization manager during pre-run
+  geometry reinitialization so stale preview-world models are not dereferenced.
+- Updated the `gdetector` example to register detector construction with the
+  Geant4 run manager before reload, matching the main executable setup.
+- Added a runtime option update helper and used it to keep the `gsystem` and
+  `runno` options aligned with setup-tab reload selections.
 - Deferred visualization scene setup until startup or reloaded geometry contains
   displayable volumes.
+- Skipped the initial `/run/initialize` in GUI sessions that start without a
+  `gsystem`, so setup-tab reloads install the first initialized geometry.
+- Replaced the GUI board newline regular expression with explicit line-ending
+  normalization to avoid invalid `QRegularExpression` warnings.
+- Made setup-tab database discovery non-fatal at GUI construction time, leaving
+  the setup view empty when the configured SQLite file is unavailable.
+- Added a detector-construction geometry-state check and used it to avoid
+  querying Geant4 volumes before startup or setup reload has built a world.
+- Added an install script that rebuilds `examples/gemc.db` from the installed
+  example geometry scripts using the installed `python_env`.
+- Made the GUI pre-run handoff remove stale visualization models, rebuild
+  geometry, and call `G4RunManager::Initialize()` before event processing.
+- Kept GUI reload system selections descriptor-only and cloned fresh systems for
+  each Geant4 construction, avoiding duplicate `root` volumes when running after
+  a setup-tab reload.
 - Better generator statistics for some examples
 - Api and analyzer moved to pygemc module 
 - Examples and tests adapted to use pygemc