Change of Quality requirements on L1muons in cross-channels: email from Vasile, 23 Feb 2009


Subject:
Quality code for muons in some cross-channel triggers
From:
Vasile Mihai Ghete <Vasile.Mihai.Ghete@cern.ch>
Date:
Mon, 23 Feb 2009 16:53:56 +0100
To:
TSG convenors <cms-mgt-triggerstudies@cern.ch>, Ivan Mikulec <Ivan.Mikulec@cern.ch>
                                                                                                                                  
hi,
                                                                                                                                  
After we discussed again the quality cuts for muons in the two new menus (L1Menu_Commissioning2009_v0  
and L1Menu_MC2009_v0), Ivan suggests to change the quality code for muons in cross-channel triggers of the type
"SingleMu_* AND (other than muons trigger objects)" to require the same quality codes as in double muon triggers.
                                                                                                                                  
The main reason would be to extend the eta coverage of the muon to  eta = 2.4 in these cross-channel triggers.
                                                                                                                                  
Cross-channel triggers of the type
"SingleMu_* OR (other than muons trigger objects)" would require further the same quality codes as in single muon trigger.
                                                                                                                                  
 The L1 muon-quality for:
                                                                                                                                  
    * Single muon triggers require quality codes: 4 or 5 or 6 or 7
    * Double muon triggers require: 3 or 5 or 6 or 7
    * Triple or quadruple muon triggers require: 2, 3, 4, 5, 6, 7
    * Muons in cross-channel triggers require the same quality codes as in single, double, triple or 
quadruple muon triggers, except for muons in cross-channel triggers of the type "SingleMu_* AND (other 
than muons trigger objects)" which requires the same quality codes as in double muon triggers.
                                                                                                                                  
From the practical point of view, if I make the changes that would mean to change in L1Menu_Commissioning2009_v0 
the names of L1_Mu3_Jet6  and L1_Mu5_Jet6  to L1_Mu3QE8_Jet6  and L1_Mu5QE8_Jet6
to keep consistent notation (Mu3 is reserved for default quality code 4 or 5 or 6 or 7 - hex F0). 
E8 is the hex for 11101000 - a wiki page will contain the hex codes  :-)
                                                                                                                                  
Default quality codes are not observed in the condition or algorithm name.
                                                                                                                                  
In L1Menu_MC2009_v0
L1_Mu3_EG5 and L1_Mu5_Jet15 would become  L1_Mu3QE8_EG5 and L1_Mu5E8_Jet15
                                                                                                                                  
If there are no complaints, I would make the changes today and, exceptionally, keep the same version of 
the menus in the menu name as we did not write the menus to DB yet.
                                                                                                                                  
                                                                                                                                  
-- Vasile

-- EmmanuellePerez - 01 Apr 2009

Edit | Attach | Watch | Print version | History: r2 < r1 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r2 - 2020-08-31 - TWikiAdminUser
 
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    Sandbox/SandboxArchive All webs login

This site is powered by the TWiki collaboration platform Powered by PerlCopyright & 2008-2023 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