1 / 6

Powering on…

Powering on…. Last week: CMS off to give evaporation time to dry out the experiment Monday – Tuesday: Began powering on CSCs All chambers HV = OK ME  2, ME  3, ME  4 LV = OK Tomorrow: Continue powering on ME–1. Near term CMS Running. 22 – 23 Oct.: Mid-Week Global Run

beverly-wilkins
Download Presentation

Powering on…

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. Powering on… • Last week: CMS off to give evaporation time to dry out the experiment • Monday – Tuesday: Began powering on CSCs • All chambers HV = OK • ME2, ME3, ME4 LV = OK • Tomorrow:Continue powering on ME–1 G. Rakness (UCLA)

  2. Near term CMS Running • 22 – 23 Oct.: Mid-Week Global Run • To include clock scan • Mon. 26 Oct.: Begin 24/7 global running in preparation for beam • CSC shifts begin Monday 26 Oct. 09:00 • Plan is: • start/stop runs as predicted for first collisions • after stop perform calibration runs • 2 shifts/week “playtime” • Restricted change control G. Rakness (UCLA)

  3. LHC Plans as of this Morning • This weekend: Injection tests to sector 3-4 (LHCb, ALICE) • 7 – 8 Nov.: Injection tests to sector 4-5 (CMS) • Injection tests = “beam splash” events…. G. Rakness (UCLA)

  4. Proposal for CSC to-do w.r.t. TMB • Wednesday: • Continue powering on detector: ME–1 • Merge TMB software with online software version currently in CVS • Currently ongoing… • After ME–1 on, change online software link to merged version and download TMB firmware (15 Oct 2009 version) to VMEm2_5 • Measure communication parameters • alct_rx_clock_delay, alct_tx_clock_delay, alct_posneg, alct_tx_posneg, cfeb[0-4]delay • Synchronize BC0 • Take a long local run, i.e., enough data to get sensible “Dayong’s plots” • Roll back TMB firmware and software • Weekend: • Assuming Dayong’s plots look OK • Download TMB firmware to system • Move to online software version EMULIB_7_12 (new TMB software) • Measure communication and synchronize BC0 in system • Monday: • Local run and make sure everything is OK… (if I somehow didn’t manage to get one on Sunday…) G. Rakness (UCLA)

  5. Xml file created for VMEm2_5 (test chamber for muonic timing) Starting from VME_minus_20091005_pretrigger3.xml… • Change the TMB Firmware dates • tmb_firmware_month="6“  “10” • tmb_firmware_day="4“  “15” • Add communication parameter alct_tx_posneg=“XX“ • to be measured • Add Time-of-flight offsets… • alct_tof_delay=“XX”  input values from Jay (next page) • tmb_to_alct_data_delay=“XX“  input values from Jay (next page) • cfeb_tof_delay="0“ • cfeb0_tof_delay="0“ • cfeb1_tof_delay="0“ • cfeb2_tof_delay="0“ • cfeb3_tof_delay="0“ • cfeb4_tof_delay="0" • Make LCT0 BC0 from TMB, LCT1 BC0 from ALCT • Add mpc_sel_ttc_bx0="0“ • Change alct_bx0_enable="0" to alct_bx0_enable="1" • Change tmb_bxn_offset=“XX”  “3540” • Variable: will affect absolute offset of RX (see next page) • Change alct_bxn_offset=“XX”  “0” • With muonic timing, BXN should = 0 @ BC0… (may need to change depending on ALCT latching of BC0 signal) G. Rakness (UCLA)

  6. Muonic timing parameters from Jay to be used in the test xml • Set mpc_tx_delay="0" • Replace afeb_fine_delay values with FAST site values (to compensate for AFEBALCT cable lengths) Input values… • TX == tmb_to_alct_data_delay • tx == alct_tof_delay • Chamber TX tx RX rx • ME-2/1/14 8 0 8 0 • ME-2/1/15 7 12 8 0 • ME-2/1/16 7 9 7 10 • ME-2/2/27 8 8 7 11 • ME-2/2/28 9 0 8 4 • ME-2/2/29 9 3 8 6 • ME-2/2/30 9 0 8 4 • ME-2/2/31 8 10 8 2 • ME-2/2/32 8 10 8 2 Values to be measured to compare with above predictions… • RX = alct_bx0_delay (= match_trig_alct_delay) • Rx = alct_rx_clock_delay G. Rakness (UCLA)

More Related