1. 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
  2. 15 May, 2020 1 commit
  3. 14 May, 2020 3 commits
  4. 13 May, 2020 1 commit
  5. 12 May, 2020 4 commits
  6. 11 May, 2020 3 commits
  7. 08 May, 2020 2 commits
  8. 06 May, 2020 6 commits
  9. 05 May, 2020 1 commit
  10. 04 May, 2020 1 commit
    • Savanna Shaw's avatar
      Avoid changing collection names in muon trigger sequences · 02c022cc
      Savanna Shaw authored
      Removing a few instances where we were defining a track particle container name (and also an algorithm name) globally within different muon sequences, which can cause problems depending on which order chains are configured in the menu (since the names were being overwritten). All the sequences that need the track particle collection name use the same default variable name that we define only once. All sequences that were changing the collection name did not have any later dependency on the new name in other sequences.
      02c022cc
  11. 02 May, 2020 1 commit
  12. 30 Apr, 2020 3 commits
  13. 28 Apr, 2020 1 commit
    • Will Taylor's avatar
      Cause test to fail if any step fails · e03ea2da
      Will Taylor authored
      Prior to this change, a successfully generated menu in a previous test run
      could still exist after making changes, which verify_menu_config would then
      run on potentially causing the test to pass even if there was an exception
      whilst generating the menu.
      e03ea2da
  14. 27 Apr, 2020 1 commit
  15. 26 Apr, 2020 2 commits
  16. 25 Apr, 2020 1 commit
  17. 24 Apr, 2020 2 commits
  18. 22 Apr, 2020 3 commits
  19. 21 Apr, 2020 1 commit
  20. 20 Apr, 2020 2 commits
    • Savanna Shaw's avatar
      Updates to the muon newJO config for the muon trigger · 6aed0c16
      Savanna Shaw authored and Frank Winklmeier's avatar Frank Winklmeier committed
      This is a first attempt to add the MuonCombinedMuonCandidateAlg to the trigger newJO test. It's not quite working yet, so is added but commented out. Some modifications to the configuration does bring it closer to running:
      
      - Added two new flags for the muon trigger: one general one that can cover the generic trigger configuration differences, and one SA muon specific flag since we configure some tools differently for SA muons than for combined muons in the trigger. Both flags are false outside of running the trigger.
      - Fixed a small misconfiguration of one property for the CaloTrackStateOnSurfaceTool.
      - Updated the configuration of several relevent tools for the trigger using the newly introduced flags.
      6aed0c16
    • Will Taylor's avatar
      ebf7d14a