%CERTIFY%

DraftMTSGTasksOct2017

Open Muon Trigger Tasks / Roles

For more details, contact muon trigger coordinators: Marcus Morgenstern (marcus.matthias.morgenstern@cernNOSPAMPLEASE.ch) and Mark Owen (markowen@cernNOSPAMPLEASE.ch). Items marked with a Star (full) are high priority / higher profile items.

  • Coordinator of muon trigger on-call
    • Maintenance of muon trigger on-call tools and web pages
    • Try to collect information which could possibly affect the muon trigger, and update the shifter web page accordingly
    • OTP: Class 3. Not a qualification task.
    • FTE: 0.1

  • Star (full) Coordinator of muon trigger validation
    • Coordination of development and maintenance of trigger validation tool
    • Coordination of keeping watching trigger performance and report it at the muon trigger meeting
    • OTP: Class 3. Not a qualification task.
    • FTE: 0.2

  • Star (full) Contact person for muon trigger matching tool and scale factor tool
    • Maintenance of TrigMuonMatching package and Maintenance of trigger scale factor tool in MuonEfficiencyCorrections package. The task could also be split in two, but someone covering both would likely be more optimal.
    • Prequisite: c++ and knowledge of the analysis release code would be beneficial
    • OTP: class 3. Not a qualification task
    • FTE: 0.2 for 15 months (to cover the rest of run 2), but the effort will not be uniform (i.e. more effort needed when e.g. scale factors need to be updated)

  • Contact person for TrigMuonHypo package
    • Maintenance of TrigMuonHypo package package
    • Prequisite: c++, python and athena experience would be beneficial
    • OTP: class 3. Not a qualification task
    • FTE: 0.1 for 15 months (to cover the rest of run 2)

  • Star (full) Trigger scale factor measurements for 2018 data
    • The performance of the muon trigger can be measured using the Z tag-and-probe method. The task would be to perform these measurements on the rest of the run 2 data and MC, providing the scale factors that will be used for the physics analyses of the run-2 data. There is also the possibility to make a publication containing these measurements.
    • Prequisite: c++ experience would be beneficial
    • OTP: class 3. Not a qualification task
    • FTE: 0.2 for ideally ~17 months (to cover the rest of run 2)

  • Optimization of EF full scan for low pT muons
    • Current EF full scan algorithm was optimized for muons above 8GeV pT. We are seeing inefficiency compared to Run1 in low pT region, ~5GeV, and this is what we would like to improve.
    • Prerequisite: Some C++ and python of advantage
    • OTP: class 3. Would need to be combined with other work to be enough for a qualification task.
    • Duration: 0.5 FTE for 2 months

  • Use of muon quality to optimize the trigger rate
    • The current final stage of the HLT muon trigger does not apply any specific quality cuts on the selected muons. A possible way to reduce the trigger rate would be to apply quality cuts (e.g. on the chi2 of the track fit) to reduce the trigger rate.
    • Prerequisite: Some C++ and python of advantage
    • OTP: class 3. Suitable for a qualification task.
    • Duration: 0.5 FTE for 6 months

  • Star (full) Migration to AthenaMT for the precision track finding (TrigMuSuperEF)
    • For run-3, the experiment will transition to the multi-threaded AthenaMT environment. This requires transitioning the algorithm code to be able to run in the new framework. For the case of TrigMuSuperEF, we are running offline tools, so this work will need to be done in collaboration with offline experts. The task would include validating the migrated algorithm.
    • Prerequisite: Some C++ and python of advantage
    • OTP: class 3. Suitable for a qualification task.
    • Duration: 0.5 FTE for 6 months

  • Star (full) Migration to AthenaMT for the fast combination algorithm (TrigMuComb)
    • For run-3, the experiment will transition to the multi-threaded AthenaMT environment. This requires transitioning the algorithm code to be able to run in the new framework. For the case of the fast combination algorithm, this means migrating the TrigMuComb algorithm to the new base class and ensuring all the data and tool access is thread safe. The task would include validating the migrated algorithm.
    • Prerequisite: Some C++ and python of advantage
    • OTP: class 3. Suitable for a qualification task
    • Duration: 0.5 FTE for 6 months

  • Star (full) Migration to AthenaMT for muon hypothesis algorithms
    • For run-3, the experiment will transition to the multi-threaded AthenaMT environment. The new framework for the trigger requires that the different hypotheses (pT cuts) for the different muon triggers will be applied within a single algorithm, using multiple tools, while in the old framework multiple algorithms were used. The task is to carry out this migration for the muon hypothesis algorithms and validating the migrated algorithm(s).
    • Prerequisite: Some C++ and python of advantage
    • OTP: class 3. Suitable for a qualification task
    • Duration: 0.5 FTE for 6 months

  • Full scan support for MuGirl
    • Prerequisite: Some C++ and python of advantage, suitable for student
    • Duration: 0.5 FTE for 6 months

  • Configuration update in muon HLT so that HLT muon can run alone while offline muon is turned off in athena


Major updates:
-- MarkOwen - 2017-10-05

%RESPONSIBLE% Main.unknown
%REVIEW% Never reviewed -- MarkOwen - 2017-10-05

Edit | Attach | Watch | Print version | History: r2 < r1 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r2 - 2017-10-06 - unknown
 
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    Sandbox All webs login

This site is powered by the TWiki collaboration platform Powered by PerlCopyright & 2008-2020 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
or Ideas, requests, problems regarding TWiki? use Discourse or Send feedback