RPC Hardware and Commissioning Outline Hardware installation Commissioning
- Slides: 14
RPC Hardware and Commissioning Outline • Hardware installation • Commissioning Tower test Local commissioning Global Runs A. Colaleo - INFN-BARI
UXC BARREL Status DETE detc CTO R Gas rack com m. Detecttower cables (HV-LVDCS cables) LBoxes Link Boards LV easy crates LV modules RBC Tower cables MAO W+2 ok ok Ok ok W+1 ok ok Ok ok W 0 ok ok Ok ok W-1 ok ok Jan ok 1 missing Jan? W-2 ok ok Jan Jan? Jan ok 2 missing Jan? A. Colaleo - INFN-BARI
USC BARREL Status DETECTO R HV cables – patch panel HV Easy HV distributo rs EASY – majiste – SY 1527 local cable HV multicond. Cable test Trigger cables from UXC-USC Final LV system. Power from S 4 W+2 ok ok ok 12/12 W+1 ok ok ok 12/12 W 0 ok ok W-1 14/12 Ok ok ok ok 14/12 Jan. W-2 14/12 ok ok 14/12 Jan By the end of this week we should have the final power LV system from S 4 working and all barrel fiber installation in trigger tunnel completed. Still HV modules missing in order to complete the full barrel system A. Colaleo - INFN-BARI
Commissioning bottle necks -Final gas system Still on temporary gas system. Max 6 sectors under gas. -MAO delivery schedule. Affecting the W-1, W-2 commissioning. One MAO available: to be moved from tower to tower (Pigi? ) -HV/LV Modules delivery schedule. LV modules missing for W-2 commissioning. Still HV modules missing in order to complete the full barrel system. -Trigger boards. Local commissioning with diagnostic readout depends on TB available. TB schedule (Maciek) A. Colaleo - INFN-BARI
Status of final system Final gasgas system 1. Commissioning started in October 2. Commissioning with argon (NO CHAMBERS) done on W+1, W+2, W 0. 3. Now we are re-circulation pure freon in W+1 (only in the system bypasses at the level of the final distribution- NO CHAMBERS). Ready for final mix. 4. Next steps: Test RB+2, 0 Start-up with final mix: • Humidifier Final gas mixture (mid January) - delay in the flammable gas extraction system. • • • Install and operate our GC RPC on final gas system in fill mode (== open mode) Purifier 1+Purifier 2 on line (without gas re-circulation!) A. Colaleo - INFN-BARI
Trigger system status 3 5 2 11 10 Near towers With the available trigger boards we will be able to equip 4 sectors (full wedges) Now available sect 2 -3 -10 -12 W 0, W+1, W+2. January we will add W-1, W-2 (fibers connection this week). See Maciek’s talk A. Colaleo - INFN-BARI
Commissioning steps Steps towards full system commissioning: 1. 2. 3. Local commissioning from chamber to tower : Tower tests with random trigger Local commissioning with cosmics: test with RBC-TTU system Commissioning of the full detector/DAQ/Trigger chain Global Runs A. Colaleo - INFN-BARI
Tower test with random trigger Procedure for commissioning of each half a wheel up to the Link Boards Ø Strip Connectivity and Threshold Test Ø Noise rate as a function of HV and Thresholds Ø Monitor of Current and scan as a function of HV See more in Gabriella’s talk W+2, W+1, W 0 completed W-1, W-2 : January - Lboard installation - MAO: 4 MAO needed - only 1 available (1 tower). - LV modules on W-2 A. Colaleo - INFN-BARI
Local commissioning with cosmics Up to now no opportunity to test the TTU system. Now we need to put efforts in this project. Test with RBC-TTU system is started yesterday evening on W 0 : 0) TTU trigger configuration on going 1) readout through diagnostic readout system - Trigger Board - Link Board 2 ) trigger Out to local LTC 3) local reconstruction for efficiency studies Hope to reach a stable TTU trigger and local readout configuration by the end of this week in order to be able to make a full commissioning with cosmic sector by sector starting next week. Last step : send TTU trigger to Global Trigger as "Technical Trigger“ and readout through Global DAQ. See more in Flavio’s talk A. Colaleo - INFN-BARI
RPC in GREN • Detector & link system: • W 0: sectors 2, 3, 10, 11 • W+2: sectors 10, 11 • Trigger hardware: • two Trigger Crates: (TC_1 top sectors, TC_9 bottom sectors), 3 TBs in each crate, • Sorter Crate with 2 HSB and FSB (final setup) • 2 DCC, • “cosmic”, wide-ors patterns in the PACs CMS Week, RPC Meeting, 11 December 2007 A. Colaleo - INFN-BARI GREN Results
Problems found during GREN • FED ID hardcoded in the DCC firmware (corrected, but not tested yet) only one DCC used for data taking, • The DCC issues the “warning” state and can not recover from it (under investigation) the RPC DAQ was not used in the long runs of the last days of GREN; the data were taken with the local readout. • “Bus Errors” in the VME crates (a few per day), • “CCU Errors” in the Link Board control system (FEC-CCU) (under investigation, in contact with the CCU experts), • Loosing of the QPLL lock on the LBs (a few time per day) and “TTCrx ready” on the TC – problems with the TTC signal? CMS Week, RPC Meeting, 11 December 2007 A. Colaleo - INFN-BARI GREN Results
CR Organization Run Coordination DAQ/Trigger RPC Trigger Operation Manager TC/DPG Shift Leader Shift Operatio n RPC Experts Trigger XDAQ PVSS GAS Shift Data Quality DQM DB Event Display CMS Week RPC Meeting, 11 December 2007 A. Colaleo - INFN-BARI GREN Results
GREN Organization Improved operation procedure and shift organization https: //twiki. cern. ch/twiki/bin/view/CMS/Muon. RPC Thanks to all people A. Colaleo - INFN-BARI
Commissioning in 2008 Need to go in the configuration of continuous commissioning phase in order to - Check performance of all system (detector, trigger, DAQ) -Provide trigger to other subsystem -Setup final operation procedures -be prepared to any integrate test : GRs. Combined DT / RPC data taking organization. First meeting concerning organization and schedule next Friday at 9 o'clock in grey barrack. A training session about how to run minidaq and configure trigger will be organized (around middle of January). So please try to connect via VRVS to the meeting on next Friday. We need to provide a list of people for the training session in January and make a planning together with DT, DAQ, Trigger people. A. Colaleo - INFN-BARI
- Topic sentence outline example
- External computer hardware
- Rpc and rmi in distributed system
- Rmi vs rpc
- Asynchronous rpc
- Rpc message format
- Rpc diagram
- Rpc semantics in the presence of failures
- Communication protocols for rpc
- Rpc woerden
- Statutory rape rpc
- List some remote procedure call (rpc) issues.
- Beton proporcje
- _vti_bin exploit
- Rpc implementation in distributed system