Skip to content
Snippets Groups Projects
  1. Feb 13, 2018
  2. Feb 09, 2018
  3. Feb 08, 2018
  4. Feb 07, 2018
  5. Feb 05, 2018
  6. Feb 04, 2018
  7. Feb 03, 2018
    • Vakhtang Tsulaia's avatar
      Merge branch 'naming.Gauginos-20180202' into 'master' · 547f7d94
      Vakhtang Tsulaia authored
      Gauginos: Comply with ATLAS naming conventions.
      
      See merge request atlas/athena!8522
      
      (cherry picked from commit e7dfcaac [formerly 30cd7ea9eb70b35f23c435d93807f5241017a1e3])
      
      4037fd93 Gauginos: Comply with ATLAS naming conventions.
      
      Former-commit-id: c3a365c60423174097e78055fad68db6606679b3
      547f7d94
  8. Feb 02, 2018
  9. Feb 01, 2018
    • Vakhtang Tsulaia's avatar
      Merge branch 'naming.Charginos-20180201' into 'master' · ffcbc1e9
      Vakhtang Tsulaia authored
      Charginos: Comply with ATLAS naming conventions.
      
      See merge request atlas/athena!8504
      
      (cherry picked from commit 06f75037 [formerly fc447cad])
      
      7207c79c Charginos: Comply with ATLAS naming conventions.
      
      Former-commit-id: b54f4b25ac6c619543e7dbb834613d4f67d399ef
      ffcbc1e9
    • John Chapman's avatar
      Dropping unnecessary Geant4 UI command calls · 28369de8
      John Chapman authored
      During a discussion with the Geant4 experts about Geant4 UI commands
      it was noted that the command `/geometry/navigator/check_mode true`
      was being issued in `G4AtlasAlg` and `TransportTool`. Due to the point
      in the initialization at which this is called it currently has no effect,
      but if it were to be run it would greatly slow down simulation jobs
      due to the extensive testing which it activates.
      
      For this reason these calls are being dropped, to remove any possibility
      of the code being activated in current/future production jobs.
      
      See ATLSASIM-3454 for more discussion of how `G4UICommands` are used in
      ATLAS simulation code.
      
      
      Former-commit-id: 02b61a2426c21d04058d2035134fada217ba51a2
      28369de8
    • John Chapman's avatar
      Minor bugfix for CfgGetter method for VolumeDebuggerTool · 5ec5dc03
      John Chapman authored
      While working on ATLASSIM-3556 a minor configuration issue was found
      in the `CfgGetter` method for the `VolumeDebuggerTool`.
      
      
      Former-commit-id: 1332d9357c03097c7a1baf68ad61b9144e6a9e28
      5ec5dc03
    • John Chapman's avatar
      Add functionality to TruthIncident classes to pick up pre-defined decays · 166b19dd
      John Chapman authored
      When we are running with quasi-stable particle simulation switched on it
      is very useful to know what kind of interaction we are dealing with when
      the `TruthSvc` comes to update the truth information. For this purpose the
      interface of `ITruthIncident` has been extended to include an
      `int interactionClassification() const` function. This returns zero in
      the default implementation the function is then overloaded in
      `Geant4TruthIncident` to use the the information from the current `G4Track`
      to determine the nature of the interactions. There are four different
      interaction classifications. Described as follows:
      
       - case 0: interaction of a particle without a pre-defined decay;
      
       - case 1: a particle with a pre-defined decay under-going a
                 non-destructive interaction;
      
       - case 2: a particle with a pre-defined decay under-going a
                 destructive interaction other than its pre-defined decay;
      
       - case 3: a particle under-going its pre-defined decay.
      
      These will allow the TruthSvc to manipulate the `GenEvent` in different
      ways in each case. This commit will help the work in ATLASSIM-3313.
      
      
      Former-commit-id: cbb8cb5c71822c400bcc9565df9396a94fe7c4fc
      166b19dd
  10. Jan 30, 2018
  11. Jan 27, 2018
  12. Jan 26, 2018
  13. Jan 25, 2018
Loading