Skip to content
Snippets Groups Projects
  1. Dec 04, 2020
  2. Oct 08, 2020
  3. Oct 07, 2020
    • scott snyder's avatar
      xAODCoreAthenaPool: Fixes for writing ShallowAuxContainer with variable vetoes. · bd59832d
      scott snyder authored
      Vetoing variables from a ShallowAuxContainer had a couple problems.
      
       - When testing for whether we can do a simple copy, we also need to check
         that there are no variable vetoes.
       - Fix setting of number of elements to be copied in the case of 
         variable vetoes but no thinning.
       - When we copy variables, the new container should always be set 
         for shallowIO.  All the variables we want to write will be copied
         to the new container.  Any that are in the parent but not the new
         container will have been explicitly vetoed.
      bd59832d
    • scott snyder's avatar
      Fix warning · 173b6afd
      scott snyder authored
      173b6afd
    • scott snyder's avatar
      ByteStreamCnvSvc: Byte stream metadata adjustments. · 1cee99c6
      scott snyder authored
      Don't crash in ByteStreamEventStorageOutputSvc if there's no 
      bytestream metadata.  (Can happen for example if we're reading pool
      and writing bytestream.)
      
      In RDP_ByteStream_jobOptions, add EventInfo as an additional dependency
      of StreamBS.  (Needed for SCT_RawDataByteStreamCnv tests.)
      1cee99c6
  4. Oct 06, 2020
  5. Oct 05, 2020
    • Frank Berghaus's avatar
      Use the GaudiKernel to handle ouput service interface · 39cec181
      Frank Berghaus authored and Vakhtang Tsulaia's avatar Vakhtang Tsulaia committed
      The extends template takes care of the onerous tasks of implementing the
      functionality required for interactions with the service interface. This
      just streamlines the code a bit and ensures the interface accessors are
      correctly implemented.
      39cec181
    • Bertrand Martin Dit Latour's avatar
      auRecTools: use consistently tau track IP w.r.t. tau vertex · 1e4cfb41
      Bertrand Martin Dit Latour authored and Vakhtang Tsulaia's avatar Vakhtang Tsulaia committed
      Hello,
      
      This MR is harmonising the use of tau track IP and IP significance parameters across the tau reconstruction.
      We now use everywhere the impact parameters w.r.t. the tau vertex instead of w.r.t. beam line (relevant for d0).
      New methods are introduced to retrieve the track IP and IP significances directly from the tau track (before, we would use e.g. d0 from the associated TrackParticle, i.e. d0 w.r.t. the beam line).
      
      Because we need track IPs early in the reconstruction (right after tau vertex finding and tau track association, and before tau track classification), I had to move the track IP calculation from TauVertexVariables to TauTrackFinder, as TauVertexVariables is scheduled late in the reconstruction chain.
      
      Two variables have been discontinued: TauJetsAux.ipSigLeadTrk TauJetsAux.ipZ0SinThetaSigLeadTrk. These are track IPs defined for the leading track. Now that we compute these for all tau tracks, we can drop these "leading track" variables.
      
      Using standalone tau reconstruction from ESD, I have checked that the tau reconstruction output is unchanged if I fall back to the "old" calculations for track IPs, i.e. if I set d0TJVA = track()->d0(), and z0sinthetaTJVA = z0sinThetaTJVA(tau) in Track_v1.
      Meaning, this MR is mostly code reorganisation. The only modification that changes the reconstruction is the new definition of d0TJVA and z0sinthetaTJVA.
      With these new definitions, we get slight changes on the BDT ID score and the RNN ID score, as well as the track classification scores, as expected.
      
      Cheers,
      Bertrand
      1e4cfb41
  6. Oct 02, 2020
  7. Oct 01, 2020
  8. Sep 30, 2020
    • sutt's avatar
      Replace use of old RegSelSvc by RegSelTools for the ID · 2a6c88e9
      sutt authored
      The single RegSelSvc is to be replaced by a separate RegSelTool for each subsystem.
      
      This merge request is to implement that migration for the ID code.
      
      This code contains about 60 % of all the changes that are needed for the migration,
      and most of the changes for the pixel, SCT and TRT.
      
      ```
      For information the packages needing changes are
      Innerdetector/InDetEventCnv/PixelRawDataByteStreamCnv
      InnerDetector/InDetEventCnv/TRT_RawDataByteStreamCnv
      InnerDetector/InDetExample/InDetRecExample
      InnerDetector/InDetRecAlgs/InDetPrepRawDataFormation
      InnerDetector/InDetRecTools/TRT_SeededSpacePointFinderTool
      
      Reconstruction/TRT_Rec
      Reconstruction/iPat/iPatRecExample
      
      Innerdetector/InDetExample/InDetTrigRecExample
      
      InnerDetector/InDetTrigRecAlgs/InDetTrigPrepRawDataFormat
      InnerDetector/InDetTrigRecAlgs/InDetTrigRawDataProvider
      InnerDetector/InDetTrigRecAlgs/SiTrigSPSeededTrackFinder
      InnerDetector/InDetTrigRecAlgs/SiTrigSpacePointFormation
      InnerDetector/InDetTrigRecAlgs/TRT_TrigSeededTrackFinder
      InnerDetector/InDetTrigRecAlgs/TRT_TrigTrackSegmentsFinder
      
      Trigger/TrigTools/TrigOnlineSpacePointTool
      Trigger/TriggerCommon/TriggerJobOpts
      
      Trigger/TrigAlgorithms/TrigGenericAlgs
      Trigger/TrigAlgorithms/TrigT2MinBias
      Trigger/TrigHypothesis/TrigLongLivedParticlesHypo
      ```
      
      plus the configuratin for every package that uses any of the above packages which will need to
      instantiate the RegSelTools for the tool and algorithms configurables.
      2a6c88e9
  9. Sep 28, 2020
  10. Sep 23, 2020
  11. Sep 22, 2020
  12. Sep 21, 2020
  13. Sep 19, 2020
  14. Sep 18, 2020
  15. Sep 17, 2020
  16. Sep 14, 2020
  17. Sep 11, 2020
  18. Sep 09, 2020
Loading