Add configuration for the Detailed Timing feature
@gcorti @adavis @kreps @admorris
This adds all the necessary configuration in python needed to activate the DetailedTiming feature from Gaussino. By default it will detect all the sub-detectors that were used for the specific datatype and geometry service (DetDesc/DD4hep). Information about the time spent by Geant4 in each subdetector, per thread, per particle and per physics process will be printed to the standard output and CSV files. One can also overwrite the defaults and print all the G4 volumes and see which were matched.
@tlatham @bcouturi
DetDesc for Run1/2 and Run3 works in a similar way to what was implemented in Sim10. The problematic one is DD4hep. In particular, and this is just one of a few obstacles, some G4 volumes cannot be matched to the corresponding sub-detectors because there is no sub-detector name/hint in their path. That is different from what we have in DetDesc, where each path has a long prefix, separated by forward slashes, with the detector name in between. For example, in DD4hep Muon (FYI @edelucia) and Ecal (FYI @dmanuzzi) introduce volumes like: AV_2102!GasGapLayer7_3#3!G10GapBox_1#1 or lvMidCellPb_42, impossible to match with the corresponding sub-detectors. On the other hand, in DetDesc we have volumes
That means that the detailed timing feature will not measure the time correctly for DD4hep unless we introduce sub-detector prefixes in the Detector project.
Examples
All examples below were produced with the same number of events and beam options:
-
50events, - 6.5 TeV as in Run2,
- minbias.