This project is mirrored from https://:*****@gitlab.cern.ch:8443/atlas/athena.git. Pull mirroring updated .
  1. 20 Oct, 2021 1 commit
  2. 12 May, 2021 1 commit
    • Frank Winklmeier's avatar
      TriggerMenuMT: add custom log formatter · 62a6601e
      Frank Winklmeier authored
      Add a custom `logging` formatter for all child loggers in the
      TriggerMenuMT package. Due to the deep module hierarchy, logger names
      often become too long and make log file reading difficult. The custom
      formatter now only shows the first and last module name, e.g.:
      
      Py:TriggerMenuMT.HLTMenuConfig.UnconventionalTracking.FullScanLRTConfiguration
      becomes
      Py:TriggerMenuMT:FullScanLRTConfiguration
      
      Also remove all custom logger names and use the module `__name__`
      consistently.
      62a6601e
  3. 13 Aug, 2020 1 commit
  4. 10 Aug, 2020 1 commit
  5. 28 Jan, 2020 1 commit
    • Joerg Stelzer's avatar
      Restructuring config data classes · be71e4ec
      Joerg Stelzer authored and Adam Edward Barton's avatar Adam Edward Barton committed
      Prior all DataStructure-derived classes were holding a copy of the
      ptree that they were constructed from. Now they hold either a
      reference (ptree*) or own the original (shared_ptr<ptree>).
      
      Basically the objects L1Menu, HLTMenu, and L1-/HLTPrescaleSet will hold
      the ptree created from the json files. All sub structures will only have
      a pointer to the sub-tree which is part of the big ptree.
      
      This avoids copying ptree's around and inflating the size of the menu.
      One has to be carefull when creating the sub-structure and only pass
      references to sub-trees of the original tree to the constructors.
      be71e4ec
  6. 29 Aug, 2019 2 commits
    • Joerg Stelzer's avatar
      Generation of L1 menu for run 3 (Part I) · 24c64be4
      Joerg Stelzer authored
      First version (fairly complete) to generate the Run 3 L1 Menu. Main
      points:
      * The L1Menu and L1TopoMenu have been merged
      * There are three directories:
        - L1/Menu for the menu definition
        - L1/Config for the threshold and item definition and cabling layout, and
        - L1/Base for classes to hold the menu in place
      
      Start assembling an MC_pp_v8 menu. The menu remains split into 2 files,
      a file Menu_x that defines the items, and a file Menu_x_inputs, which
      defines the configuration of the topo boards, muctpi and ctpin. A third
      Menu file exists for the legacy inputs.
      24c64be4
    • Joerg Stelzer's avatar
      Generation of L1 menu for run 3 (Part I) · 32cc8fde
      Joerg Stelzer authored
      First version (fairly complete) to generate the Run 3 L1 Menu. Main
      points:
      * The L1Menu and L1TopoMenu have been merged
      * There are three directories:
        - L1/Menu for the menu definition
        - L1/Config for the threshold and item definition and cabling layout, and
        - L1/Base for classes to hold the menu in place
      
      Start assembling an MC_pp_v8 menu. The menu remains split into 2 files,
      a file Menu_x that defines the items, and a file Menu_x_inputs, which
      defines the configuration of the topo boards, muctpi and ctpin. A third
      Menu file exists for the legacy inputs.
      32cc8fde