1. 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
  2. 21 Apr, 2021 1 commit
    • Savanna Shaw's avatar
      Fixes for cosmic trigger tests in MC · 16ed833d
      Savanna Shaw authored and Edward Moyse's avatar Edward Moyse committed
      A couple of fixes for cosmic trigger MC tests (ATR-23207):
      - Adding BG3 (EMPTY) to the bunch group set and setting ForceBunchGroupPattern=True for the CTP simulation when running in cosmics mode so that the EMPTY L1 triggers are active.
      - Updating the MC art tests to include the doCosmics=True option so that the everything (including the HLT reconstruction) is configured for cosmics.
      16ed833d
  3. 15 Apr, 2021 1 commit
  4. 13 Apr, 2021 1 commit
  5. 07 Apr, 2021 1 commit
  6. 05 Apr, 2021 1 commit
  7. 22 Mar, 2021 1 commit
  8. 01 Feb, 2021 1 commit
  9. 28 Jan, 2021 1 commit
  10. 05 Nov, 2020 1 commit
  11. 27 Oct, 2020 1 commit
  12. 02 Oct, 2020 1 commit
  13. 24 Sep, 2020 1 commit
  14. 04 Sep, 2020 1 commit
  15. 13 Aug, 2020 1 commit
  16. 10 Aug, 2020 1 commit
  17. 09 Jul, 2020 1 commit
  18. 27 Jun, 2020 1 commit
    • Joerg Stelzer's avatar
      L1Calo config consolidation · 31987fbc
      Joerg Stelzer authored
       * Threshold values and ptMinToTopo stored internally in MeV as unsigned int
       * Access methods in MeV, GeV (float), and counts (using energyResolution)
       * Change "emscale" and "jetscale" to "resolutionMeV" in the menu and C++ sw
       * Added eta-dependend pTMinToTopo to jFEX jets
       * Fix EM*V thresholds in the menu such that the eta-ranges and thrvalues match Run 2
       * Some cleanup of ThresholdDefLegacy.py and ItemDef.py to reduce dependence on menu version
       * Added XS definition in menu and access software
       * Added L1Calo specific base class for L1Thresholds (many commonalities between L1Calo thresholds that don't apply to L1Muon thresholds)
       * Change RangeValue from struct to class with proper access functions to member variables
       * Restructur of upload() member function to avoid calling virtual methods in constructor
       * FIX BUG: access to TopoAlgs by output is working now
      31987fbc
  19. 15 May, 2020 1 commit
  20. 13 May, 2020 1 commit
  21. 11 May, 2020 2 commits
  22. 06 May, 2020 1 commit
  23. 12 Apr, 2020 3 commits
  24. 05 Mar, 2020 1 commit
    • Joerg Stelzer's avatar
      Python 3 fixes · f0790b53
      Joerg Stelzer authored
      * filter behaves differently in python 3 (can be called only once)
      * dictionaries key order follows insertion
      * json dump separators explicitly specified to create uniform behavior
      As a result L1 menus generated in python 2 and python 3 are now
      identical
      
      Fixes ATR-21075
      f0790b53
  25. 04 Mar, 2020 1 commit
  26. 03 Mar, 2020 1 commit
  27. 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
  28. 18 Dec, 2019 1 commit
    • scott snyder's avatar
      TriggerMenuMT: python3 fixes · e7465bba
      scott snyder authored
       - cmp
       - no destructuring for lambda arguments
       - xrange -> range
       - Fix relative imports.
       - generators -> list
       - iteritems
       - fix use of filter on strings
       - can't use -1 for level in __import__
       - duplicate enum value
       - except statment syntax.
       - func_name
       - izip
       - integer literals starting with 0
       - exec can't set local variables
       - sorting
       - integer vs float division
      e7465bba
  29. 14 Oct, 2019 1 commit
  30. 08 Oct, 2019 1 commit
  31. 11 Sep, 2019 1 commit
  32. 01 Sep, 2019 1 commit
  33. 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