Gaussino merge requestshttps://gitlab.cern.ch:8443/Gaussino/Gaussino/-/merge_requests2022-09-23T10:20:16+02:00https://gitlab.cern.ch:8443/Gaussino/Gaussino/-/merge_requests/87Draft: Visualize hits in Phoenix2022-09-23T10:20:16+02:00Filip BilandzijaDraft: Visualize hits in PhoenixFYI: @mimazureFYI: @mimazureGeant4 & Phoenix VisualizationMichal MazurekMichal Mazurekhttps://gitlab.cern.ch:8443/Gaussino/Gaussino/-/merge_requests/83Draft: Enable conditional storing of G4Trajectories2023-08-17T15:03:16+02:00Michal MazurekDraft: Enable conditional storing of G4Trajectories@gcorti The possibility to store G4Trajectories was not introduced when porting `GaussPostTrackAction` to Gaussino as a `TruthFlaggingTrackAction`. Now the possibility to store them is back and switched off by default.
- Set `m_storeTra...@gcorti The possibility to store G4Trajectories was not introduced when porting `GaussPostTrackAction` to Gaussino as a `TruthFlaggingTrackAction`. Now the possibility to store them is back and switched off by default.
- Set `m_storeTrajectories` if you wish to store trajectories that correspond to MCTruth from `GaussinoTrackInformation`.
- Set `m_storeMarkedTrajectories` if you wish to store only the G4Trajectories that participated in the creation of hits in the sensitive detector classes.
@fbilandz with this option we may now optimize the number of G4Trajectories used in G4 visualization in !70 and Phoenix in !78Geant4 & Phoenix VisualizationGloria CortiGloria Cortihttps://gitlab.cern.ch:8443/Gaussino/Gaussino/-/merge_requests/70Draft: Geant4 & Phoenix Visualization2024-01-18T15:30:16+01:00Michal MazurekDraft: Geant4 & Phoenix VisualizationThis is the base MR for all the developments that add/modify components that enable visualization with Geant4.
### Changes in GiGaMT
Geant4 visualization does not work out of the box with Gaussino. This is mainly because a custom even...This is the base MR for all the developments that add/modify components that enable visualization with Geant4.
### Changes in GiGaMT
Geant4 visualization does not work out of the box with Gaussino. This is mainly because a custom event loop has been implemented and many functionalities of both the `G4MTRunManager` and `G4WorkerRunManager` have been re-implemented. Additional difficulty arises from the fact that visualization in G4 is handled by an additional thread (created by Geant4 just before run initialization). This thread needs to have a few things correctly set up or otherwise it will not be created. Moreover, the worker pilot must not delete the `G4Event`s too early as they are scheduled for postprocessing in Geant4. Therefore, the following MRs adapt `GiGaMT` to the new mechanism (tested with 8 threads and > 100 events):
- !77 postpone the deletion of G4Events
- !76 add the possibility to launch UI commands before the initialization of the run
- !74 some extra information that has to be passed correctly to G4
- !69 support `EventAction` and improve `RunAction` UI commands
- !71 terminate the G4 Run correctly
- !72 do not ignore the status of the UI commands launched from the worker threads,
- !73 do not repeat `RunAction` commands that were previously used by the master thread.
- !83 conditional storing of G4Trajectories,
- !78 Add GiGaMTPhoenix
## Changes in this MR
This MR consists of:
- [x] (base) Gaussino's implementation of G4VisManager
- [x] (base) python configuration
cc: @fbilandzGeant4 & Phoenix VisualizationMichal MazurekMichal Mazurek