Analysis of Oct. 04 Test Beam RPC Data

Slides:



Advertisements
Similar presentations
MDC-II LVL-1 Trigger Khaled Teilab for the MDC Trigger Team.
Advertisements

TMB-RAT Software Update USCMS Slice Test Rice University August 16, 2004 Martin Von der Mey / Yangheng Zheng* University of California, Los.
TMB and RAT Status Report Endcap Muon OSU April 16, 2004 Yangheng Zheng University of California, Los Angeles  TMB Status  RAT Status.
US Test Beam Results Of Front End Timing T. Ferguson, N. Terentiev* (Carnegie Mellon University) CMS EMU Meeting University of California, Davis Feb 25.
CSC Synchronization Procedure and Plans CMS Endcap Muon FNAL October 29, 2004 Jay Hauser* / Martin Von der Mey / Yangheng Zheng University of.
Endcap Muon meeting: FNAL, Oct , 2004 J. Hauser UCLA 1 TMB and RAT Status Report Jay Hauser University of California Los Angeles.
Endcap Muon meeting: CMU, Oct 19, 2003 J. Hauser UCLA 1 CSC Trigger Primitives Test Beam Studies Main Test Beam 2003 Goals: Verify the peripheral crate.
DRAFT version Oct. 15, 2004 Hauser/Mey UCLA 1 Analysis of Oct. 04 Test Beam RPC Data Jay Hauser, Martin von der Mey University of California Los Angeles.
Jay Hauser, Emu meeting at Florida, 9 January CSC Trigger Meeting Summary Cast of many.
Preliminary Results from Structured Beam Test CMS Trigger Meeting June 3, 2003 Brian Mohr UCLA Dept. of Physics.
DRAFT version Oct. 15, 2004 Hauser/Mey UCLA 1 Analysis of Oct. 04 Test Beam RPC Data Jay Hauser, Martin von der Mey University of California Los Angeles.
TMB and RAT Status Report Endcap Muon OSU June 6, 2004 Martin von der Mey University of California, Los Angeles  Previous Status (OSU, April)
Trigger Bias Study at Test Bench Data RIKEN/RBRC Itaru Nakagawa.
The Track-Finding Processor for the Level-1 Trigger of the CMS Endcap Muon System D.Acosta, A.Madorsky, B.Scurlock, S.M.Wang University of Florida A.Atamanchuk,
Emulator System for OTMB Firmware Development for Post-LS1 and Beyond Aysen Tatarinov Texas A&M University US CMS Endcap Muon Collaboration Meeting October.
Monte Carlo Comparison of RPCs and Liquid Scintillator R. Ray 5/14/04  RPCs with 1-dimensional readout (generated by RR) and liquid scintillator with.
Status of the CSC Track-Finder Darin Acosta University of Florida.
7 Nov 2007Paul Dauncey1 Test results from Imperial Basic tests Source tests Firmware status Jamie Ballin, Paul Dauncey, Anne-Marie Magnan, Matt Noy Imperial.
Track-Finder Trigger at the Beam Test Results and Features Darin Acosta, Rick Cavanaugh, Victor Golovtsov, Lindsey Gray, Khristian Kotov, Alex Madorsky,
Annual Review Cern -June 13th, 2006 F. Loddo I.N.F.N. Bari RPC Electronics: Technical Trigger Flavio Loddo I.N.F.N. Bari On behalf of the RPC-Trigger group.
4 Dec 2008G. Rakness (UCLA)1 Online Software Updates and RPC data in the RAT …including Pad Bit Mapping and Efficiency… Greg Rakness University of California,
TGC Timing Adjustment Chikara Fukunaga (TMU) ATLAS Timing Workshop 5 July ‘07.
A. Meneguzzo Padova University & INFN Validation and Performance of the CMS Barrel Muon Drift Chambers with Cosmic Rays A. Meneguzzo Padova University.
CMS Latency Review, 13th March 2007CSC Trigger 1 Latency and Synchronization update.
US CMS DOE/NSF Review: June 2002, B.Paul Padley, Rice University1 CSC Muon Trigger On Detector Components B. Paul Padley Rice University June, 2002.
Track-Finder Test Beam Results Darin Acosta. Darin Acosta, University of Florida 30 July 2004 Trigger Meeting CSC Beam Test (Muon Slice Test) ME.
13 March 2007G. Rakness (UCLA) 1 RPC efficiency in RAT Greg Rakness University of California, Los Angeles UCLA phone meeting 13 March 2007.
3 Nov 2009G. Rakness (UCLA)1 Weekend of 24 – 25 October Loaded all TMB firmware –Version 15 Oct 2009 XML file created using Jay’s muonic timing constants.
US AFEB timing in CSCs in splash events, run N. Terentiev, CMU CSC Synchronization meeting Nov. 16, 2009, CERN.
TRIPLEGEM and VFATs at The Test Beam Area TRIPLEGEM and VFATs at The Test Beam Area N. Turini……reporter Eraldo Oliveri! Eraldo Oliveri main worker! N.
CMS Week, 3-7 November CSC Trigger Test Beam Report Cast of many.
SRS TIMING ANOMALY RD51 Mini-Week June 9, 2015 M. Phipps, BNL 1.
6 April 2007G. Rakness (UCLA) 1 CSC runs at minus side slice test 27 Mar – 5 Apr Color scheme: Successes Problems/questions Greg Rakness University.
Update on “Muonic Timing” of CSC Electronics
Results with the RPC system of OPERA and perspectives
Timing/Synchronization Status
CSC Synchronization Procedure and Plans
CSC EMU Muon Port Card (MPC)
University of California Los Angeles
University of California Los Angeles
Muon Track-Finder Trigger
CMS EMU TRIGGER ELECTRONICS
Noise analysis of the 1m3 DHCal test beam
University of California Los Angeles
University of California Los Angeles
University of California Los Angeles
University of California Los Angeles
Current Status of CSC Trigger Elements – Quick Summary
CSC Trigger Update Specific issues:
Darin Acosta University of Florida
September CSC Beam Test Report
ALCT, TMB Status, Peripheral Crate Layout, CSC Event Display
TMB, RAT, and ALCT Status Report
Regional Cal. Trigger Milestone: Production & Testing Complete
CSC Trigger Primitives Test Beam Studies
University of California Los Angeles
Changes in Level 1 CSC Trigger in ORCA by Jason Mumford and Slava Valuev University of California Los Angeles June 11,
TMB and RAT Status Report
Preliminary CSC Trigger Results from September Testbeam
Alon Attal Martin von der Mey Jay Hauser Mike Lindgren
CSC Trigger Meeting Summary
Effect of an ALCT SEU Much-overlooked good stuff
Bringing the ATLAS Muon Spectrometer to Life with Cosmic Rays
University of California Los Angeles
Resistive Plate Chambers performance with Cosmic Rays
PHENIX forward trigger review
Global Trigger Finds Correct BX
FED Design and EMU-to-DAQ Test
RPC approved plots.
Plans for the 2004 CSC Beam Test
Presentation transcript:

Analysis of Oct. 04 Test Beam RPC Data Jay Hauser, Martin von der Mey University of California Los Angeles

RPCs in Test Beam m- RE2, RE3 behind RE1 on ME1/2 ME3/2 ME2/2 ME1/1 1 RE1/2 (call it RE1) 2 free-standing (call them RE2, RE3) Readout info for experts only: RPC0  RE1 RPC3  RE2 RPC2  RE3 RE2, RE3 behind RE1 on ME1/2 ME3/2 ME2/2 ME1/1 m-

Link Board to RAT Board Setup RAT receives 4 cables, one from each RPC chamber Cables 0, 1, 2 were connected Appears that phasing RAT-TMB incorrect, so that 0  2 and 13 in readout N.B. RE1 seems the healthiest chamber

RPC-RAT Interface RAT receives 4 cables with 20 pairs each (3 cables active at test beam) For each cable/RPC chamber implemented: 4 bits of bunch crossing 12 bits of RPC pad data 1 clock (FYI CMS specification is 16 pads, 2 bx, 1 clock, 1 GND) New full-size backplane was used

Data Conditions Run conditions: Analysis conditions: Link boards arrived Saturday p.m., run ended Sunday evening Runs 535-548 have RPC data. Data triggered by Sector Processor, not scintillators Beam spot roughly 30 cm each dimension RAT latches bits on falling edge of 40 MHz clock where they are stable Analysis conditions: Comparison CSC chamber always ME3/2 - part of SP trigger (ALCT&CLCT required) Run 548 taken Sunday. Corrupted RPC events not included Seen at 1% level Symptom: as if no RPC cables connected to RAT (?)

TMB Bunch Crossings - Data Flat Distribution seen 0-15 (4 bits): N.B. no ALCT or TMB data transmission errors (CRC check) seen in these runs

Internal RPC BXN diff BXN difference for consecutive RPC data arriving at TMB Always incrementing by 1.

No CRC errors for TMB/ALCT ALCT CRC TMB CRC

RPC Bunch Crossings - Expectations Emu electronics used orbit=924 bx, RPC used orbit=3564 bx These are incommensurate. What are lowest 4 bits if synch is perfect? Orbit Emu BX RPC BX Emu starts (mod16) RPC starts (mod16) Difference (mod16) 1 0-923 2 924-1847 12 3 1848-2771 8 4 0-791, 792-923 2772-3563, 0-131 0, 8 4, 0 4, 8 Therefore, expect various differences in jumps of 4 bx In general, there can also be an offset due to time delay of BX0

RPC Bunch Crossings - Data TMB vs RPC see perfect agreement with expectations. At least, ALCT/CLCT bx reset/bx0 protocol = Link board protocol

RPC BX from different RPC Chambers? Nice diagonals, but offsets (2, 7 bx) due either to TTCrx offset or reset timing at Link board

Test clock sent to TMB Inverted RPC clock sent to TMB (Runs=553,554)

Reset with SPS Orbit Better agreement (run=563) Still issues to understand

Beam Spot Size Data triggered by SP covers roughly 30x30 cm (Scintillators are 10x10 cm) Key ½-Strip Key Wire Group Key ½-Strip

RPC configuration Run 562 (Wires 0-11) Run 548 (Wires 9-20)

RE1 Pad Data Quality Compare ME3/2 (rear chamber) CLCT key half-strips (not strips) to RE1 pad (vertical dimension) Good position agreement (one dead pad) Modest RPC efficiency within readout region Fiducial region for RE1 select half-strips 65-100 RPC Pad Key ½-Strip

RE1 Efficiency Within Fiducial Region Unsure exactly where pads are, so plot efficiency versus CSC wire group This RPC chamber fairly efficient Key Wire Group

RE2 Pad Data Quality Same comparison Active part of chamber appears far from beam centerlow statistics Fiducial region: select half-strips 10-50 Key ½-Strip RPC Pad

RE2 Efficiency Within Fiducial Region This RPC chamber not so efficient Key Wire Group

RE3 Pad Data Quality Same comparisons Fiducial region: select half-strips 80-115 Key ½-Strip RPC Pad

RE3 Efficiency Within Fiducial Region RE3 efficiency reaches a high value, but is not flat with wire number Key Wire Group

RPC timing versus TMB RE2 RE3 RE1

RPC versus ALCT Timing RE3 RE2 RE1 First RPC hit per chamber: RE1, RE2 all in one BX RE3 not as good Note RE1 later by 1 BX RE3 RE2 RE1

RPC Afterpulsing? RE2 RE3 RE1 Number of time bins per chamber per event RE1 and RE2 good, RE3 shows considerable after-pulsing: RE2 RE3 RE1

RPC Pads Hit Pads hit per event (summed over time bins) All look okay (RE1 slightly more pads) RE3 RE2 RE1

Summary RPC Link Board to RAT-TMB data transmission worked well RPC pads well correlated to CSC position Timing looks strange on one RPC chamber RPC efficiency hard to study Instrumented region was small Gas was not optimal due to safety concerns Will be useful to do simultaneous analysis of RPC data taken through Link board readout – is it possible to double-check? N.B. time for doing tests was way too short. Is there some way to set up a cosmic ray test bench for a longer time?