GLB, STA, trig rates, firsts ...


  • STA: 400/1990events, GLB:17/out of 400 STA
    • CSC problem? -- NO
    • halo muons (get many sta that are not matched to tracker tracks) ? -- NO


  • look at number of valid, bad,lost hits for STA muons, from DT, CSC, RPC separately, vs pT, eta.
  • verify the same info versus the trigger firing


  • in the following:
    • triga=HLT_HIL1SingleMu3_Core, trigb=HLT_HIL1DoubleMuOpen_Core
    • trk is STA or GLB, according with the caption

CSC-s (

  • staLastHitDetId_v2.pdf:
    • many bad STA, on which we most certainly trigger
    • last hit position is on second CSC station--expected for punch-through.

  • validHIts vs layer in all STA:

  • pt<10GeV, sta all:
    staPtEtaAll_ptlt10.gif staPtEtaAll.gif

  • lessons learned from the email exchange, regarding the STA reconstruction:
    • Layers 0-6:
      • a segment is labelled by the chamber alone and L=0 ('Layer=0' means the entire chamber:). segments have allocated L=0;
      • a 2D-rechit is labelled by the specific Layer L=1-6 it is on.2D hits are associated with layers 1->6;
      • the position of a segment is based on the centre of the chamber rather than a specific layer; this centre is between two layers (hence the L=0)
    • too many L=0 when requiring 'last hit position on the track', as in principle the track reconstruction uses the hits (2D or the ones from the segments)
      • Ricardo: if hits become invalid, it can happen (confirmed by me: L=0 correspond to sta-s for which nvalidHits/nhits=0)
      • Daniele Trocino:
        • two possible cases in which a stand-alone track is made of segments:
          • 1) less than two segments (DT, CSC) / hits (RPC) are marked as "valid" in the forward pattern recognition (inside-out): in this case, the remaining valid segments/hits, if any, are "invalidated" and the track will contain only invalid segments/hits. The invalid hits are not used in the global reconstruction, so the global fit will coincide with the fit in the tracker. In p-p runs at 7 TeV, about 3% of the global tracks (out of the box, no selection applied) are of such kind;
          • 2) the forward pattern recognition succeeds (>= 2 valid segments/hits), while the backward one (outside-in) fails: in this case, the outcome of the forward step is taken, so the track contains valid segments, which are used in the global fit (the fitter is flexible enough to handle hits or segments). This case is very rare: only 0.01% of the global tracks (7 TeV, no selection) is built with this kind of STA tracks.
        • Vyacheslav (long story short):
          • The forward fit and pattern reco use segments,the backward fit/smooth uses hits.
          • If the backward fit/smooth fails, you still get a track returned, in this case you get segments in return.

Trigger and offline STA and GLB

  • number of STA-s (and their pt-eta distribution) when singleMu3Core trigger fired:

nsta_triga1.gif ptEta_sta_triga1.gif

  • select the portion of luminosity that had the tracker ON (duh!) aka, there was stable beam.
mylist = ['150431:148-150431:9999']
process.source = cms.Source("PoolSource",
                            fileNames = cms.untracked.vstring("rfio:///castor/"),
                            lumisToProcess = cms.untracked. VLuminosityBlockRange(mylist),
                            noEventSort = cms.untracked.bool(True),
                            duplicateCheckMode = cms.untracked.string("noDuplicateCheck")

  • triga=HLT_HIL1SingleMu3_Core: trk=STA (left) and trk=GLB (right) for run 150431 and lumi>148, :

staPtEta_r150431_lumiGT148.gif glb_etaPt_r150431_lumiGT148.gif

  • triga=HLT_HIL1DoubleMuOpen_Core: trk=STA (left) and trk=GLB (right) for run 150431 and lumi>148, :
staPtEta_trigb1_12Ev_r150431_lumiGT148.gif glbPtEta_trigb1_5Ev_r150431_lumiGT148.gif

Now what?

  • change the trigger, to fire when having 3 stations hits (as opposed to 2); L2 trigger.-- Cath

-- CameliaMironov - 09-Nov-2010

Topic attachments
I Attachment HistorySorted ascending Action Size Date Who Comment
GIFgif glbPtEta_trigb1_5Ev_r150431_lumiGT148.gif r1 manage 8.7 K 2010-11-10 - 11:24 CameliaMironov double muon trigger
GIFgif glb_etaPt_r150431_lumiGT148.gif r1 manage 8.1 K 2010-11-10 - 10:28 CameliaMironov lumi selection
GIFgif nsta_triga1.gif r1 manage 7.8 K 2010-11-10 - 09:09 CameliaMironov singleMu3Core_nSTA
GIFgif nvalidRatioLayer.gif r1 manage 6.3 K 2010-11-09 - 20:16 CameliaMironov validHIts vs layer in all STA
GIFgif ptEta_sta_triga1.gif r1 manage 9.4 K 2010-11-10 - 09:18 CameliaMironov ptEta_triggera1
PDFpdf staLastHitDetId_v2.pdf r1 manage 138.7 K 2010-11-09 - 18:02 CameliaMironov  
GIFgif staPtEtaAll.gif r1 manage 6.0 K 2010-11-09 - 21:20 CameliaMironov all sta, pt vs eta
GIFgif staPtEtaAll_ptlt10.gif r1 manage 7.4 K 2010-11-09 - 21:20 CameliaMironov pt<10GeV, sta all
GIFgif staPtEta_r150431_lumiGT148.gif r1 manage 8.0 K 2010-11-10 - 10:27 CameliaMironov sta-s, for run 150431 and lumi>148
GIFgif staPtEta_trigb1_12Ev_r150431_lumiGT148.gif r1 manage 8.2 K 2010-11-10 - 11:24 CameliaMironov sta, double muon trigger
Edit | Attach | Watch | Print version | History: r5 < r4 < r3 < r2 < r1 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r5 - 2010-11-10 - CameliaMironov
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    Main 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