1 / 5

RPC data in RAT

RPC data in RAT. MTCC phase II global run 4188 4 chambers have RPC data: ME+1/2/28 ME+1/3/30 ME+1/3/31 ME+1/3/32 Bugs found in decoding of RPC raw hits in TMB data fixed and committed to CMSSW tag V00-09-04 (A. Tumanov) Recall, RPC raw hits in TMB data for each time bin:

natalya-penda
Download Presentation

RPC data in RAT

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. RPC data in RAT • MTCC phase II • global run 4188 • 4 chambers have RPC data: • ME+1/2/28 • ME+1/3/30 • ME+1/3/31 • ME+1/3/32 • Bugs found in decoding of RPC raw hits in TMB data fixed and committed to CMSSW tag V00-09-04 (A. Tumanov) • Recall, RPC raw hits in TMB data for each time bin: • 3 bits bxn • 12 bits pad data (= OR of [configurable] number of RPC pads) • Cuts imposed on first look at data: • 1 Local Charged Track in CSC • 1 RPC pad data bit

  2. RPC bxn • (Parity bit + single RPC pad bit) picks BXN with even number of bits • few events with odd BXN under investigation… • Have requested that parity bit be disabled…

  3. RPC pad bit vs. CSC informationME+1/2/28 • Some features: • correlation of RPC pad bit with CSC LCT position observed • Covers ~1/2 of the chamber (?) • RPC pad bit 11 never sent • map “derived” from these data under discussion…

  4. RPC pad bit vs. CSC informationME+1/3/30 • Some features: • different correlation of RPC pad bit with CSC LCT position observed • full chamber covered (ME1/3 WireGroup counts 16-48) • RPC pad bit 11 never sent • map “derived” from these data under discussion…

  5. RPC time bin • RPC data arriving at end of window in TMB… • Current configuration settings: • fifo_tbins = 12 • fifo_pretrig = 7 • rpc0_delay = 1 (default  should be added to xml file) • What to do? • Increase fifo_tbins? • Reduce fifo_pretrig? • Request reduction in link board timing topull RPC data back into window?  Is this needed for TMB to use this data in the future? • Separate the sequencer trigger fifo window and the RPC data fifo window?

More Related