1 / 8

ME1/1A—revisited…

ME1/1A—revisited…. Recall request from Wesley Smith regarding ME1/1A “We cannot remove ME1/1 at high eta from the trigger since we need every single muon trigger for startup… Please do not remove any of the sections of ME1/1 from the trigger.”. Snippet from TMB documentation:.

tod
Download Presentation

ME1/1A—revisited…

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. ME1/1A—revisited… Recall request from Wesley Smith regarding ME1/1A • “We cannot remove ME1/1 at high eta from the trigger since we need every single muon trigger for startup… Please do not remove any of the sections of ME1/1 from the trigger.” Snippet from TMB documentation: Couldn’t we just set CC[3]=0 (for TMB firmware types C and D) to enable ME1/1A in the trigger (like it used to be)? Do we want to do this? G. Rakness (UCLA)

  2. Stuff at point 5 • We have taken many local runs with detector in various states, for example… • 9 – 23 February has ME4/1 OFF while they paint the forward shielding • csc-daq03 was revived • Updated to software version 6.9, including… • monitoring package update to TMB counters (ME1/1A version) • new TMB configuration parameters… • tmb_firmware_compile_type • alct_readout_without_trig • clct_readout_without_trig • match_readout_without_trig • mpc_block_me1a • I have been pushing people to work on CSC CANbus by example • I now know more about CANbus than I ever thought possible… • … I’m surprised our CANbus worked as well as it did… G. Rakness (UCLA)

  3. Gas mixture change in CSC Recall: cost of CF4 in 2008 = CHF 400k… • CF4 reduces chamber aging in a high rate environment • Should not be necessary for commissioning with cosmic rays • Changed today at noon • 40% Ar + 50% CO2 + 10% CF4 40% Ar + 5% CF4 + 55% CO2 • How did we verify that the gas mixture was OK before we did this? • Measured mixture composition with gas chromatograph • Took local run, looked at gas gain plots in CSCValidation • Performed HV scan (see next page…) G. Rakness (UCLA)

  4. HV scan from Tuesday… https://cmsdaq.cern.ch/elog/CSC/7703 This trace is identical to January 2008 and December 2007…  Gas mixture is the same G. Rakness (UCLA)

  5. To do at point 5 • Thursday: • Continue to push CANbus studies • Calibration run • Friday: • HV scan • local data run for gas gain • Next week: cooling work will make it not possible to power on both endcaps at the same time… In the meantime… • Track finder mezzanine card test + firmware updates • Update to online software version 6.10 • Uses configuration database G. Rakness (UCLA)

  6. Beginning of shifts • From Chamonix meeting: slip in LHC schedule by ~6 weeks  Beam likely in late October… Immediate question (to be discussed at tomorrow’s commissioning meeting) is: when do we start CSC shifts? • CMS commissioning note: there are biweekly mid-week global runs beginning first week of March What would we (UCLA) like to do? • My point of view: since the power-up procedure has been fixed, it is no longer painful to turn off/on every day. I believe the major pain will be extracting volunteers to run for the mid-week global runs… G. Rakness (UCLA)

  7. Other stuff • Iterated with Alex M about including ALCT test firmware… he doesn’t think it will be a problem to include it in a beam version of ALCT firmware, but would like to see us test it out at 904 and point 5 first… G. Rakness (UCLA)

  8. To do • Get TMB + ALCT test firmware working • at 904 • At point 5 on chambers with problems • Push CANbus studies at point 5 • Come up with numbers for • (CSC latency + cable lengths) and • (RPC latency + cable lengths) so that I can decide if I believe the RPC folks about their latency… • Combine firmware version check into configuration check  moving towards a single push-button check of all configuration… G. Rakness (UCLA)

More Related