kyle stevenson elizabeth gallas terry toole trigger board meeting july 8 2003
Download
Skip this Video
Download Presentation
Transition from global_CMT-11.03 to global_CMT-12.10

Loading in 2 Seconds...

play fullscreen
1 / 5

Transition from global_CMT-11.03 to global_CMT-12.10 - PowerPoint PPT Presentation


  • 53 Views
  • Uploaded on

Kyle Stevenson Elizabeth Gallas Terry Toole Trigger Board Meeting July 8, 2003. Transition from global_CMT-11.03 to global_CMT-12.10. global_CMT over last week. 11.04 – online 10-May to July 2, one Run July 7 July 1,2 (Initial Luminosity about 20E30) 5 days with accelerator problems …

loader
I am the owner, or an agent authorized to act on behalf of the owner, of the copyrighted work described.
capcha
Download Presentation

PowerPoint Slideshow about ' Transition from global_CMT-11.03 to global_CMT-12.10' - italia


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.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript
kyle stevenson elizabeth gallas terry toole trigger board meeting july 8 2003
Kyle Stevenson

Elizabeth Gallas

Terry Toole

Trigger Board Meeting

July 8, 2003

Transition from global_CMT-11.03to global_CMT-12.10
global cmt over last week
global_CMT over last week
  • 11.04 – online 10-May to July 2, one Run July 7
    • July 1,2 (Initial Luminosity about 20E30)
    • 5 days with accelerator problems …
    • July 7 (Trigger verification run after many changes, access)
  • 12.10 online July 7,8 (2 Stores including current)
    • Smooth running with strong evidence of trigger problems effecting the trigger rates
      • L1 Cal (hot towers)
      • L3 cal: spikes, jumps, rises in L3 accept rate of JET triggers
global cmt 12 10 runs rates
global_CMT-12.10 – Runs/Rates
  • 12.10 online July 7 and July 8
    • 2 Stores incl. current store, Initial Luminosity ~30E30

Store Run LumI / PSFile PeakRates ( 1400 / 800 / 50 Hz)

2768 178721 30 / 30 700 / 460 / 45 (last run of 11.04)

178722 24 / 25 1700*/ 600 / 55*

178723 20 / 20 1400 / 550 / 60*

178724 17 / 17 1120 / 450 / 55*

2770 178733 31 / 30 1250 / 740 / 65*

178734 24 / 30 900 / 550 / 50 (L3 MET problem)

178735 22 / 20 1550 / 600 / 70*

Summary: 12.10 current rates to tape are too high, require immediate prescale adjustments !!!

global cmt 12 10 problems
Global_CMT-12.10 - problems
  • Run 178722
    • L1 and L3 spike in all high ET Jet, MHT but not MET or EM ?
      • Spike in L1 magnified in L3 ???
        • Lifetime just one or a few luminosity blocks
    • Weird correlated increase in feb with increase in rate
      • Suspect ? Increase occupancy in tracking increases candidates
  • Run 178733
    • L1 hot tower addressed by Dan
  • Run 178734
    • Jump and/or steady rise of high Et Jet, EM, MET, MHT L3 rates
      • See E1_SHT20, JT_95TT, MET and MJT triggers (but not lowest ET jets)
      • Continues over many luminosity blocks
global cmt 12 future
Global_CMT-12.– future
  • Dmitri/Arnd: Rate caps for version 12
    • L1 / L2 / L3 Accept = 1400 / 800 / 50 Hz
  • L3 Calorimeter problems observed for JET triggers
    • May be other problems, these have cause most blatant rate problems
  • Rates are too high
    • Prescale changes based on data collected are being applied at L1 to control rate to tape
    • TM so far have changed only the 25E30.prescales
      • See the change.log for exact changes
      • This was because we expected it to be used in next store (this morning)
      • 25E30 file was skipped during store today (due shifter error)
    • Accepting input
  • Future:
    • No trigger change requests have been received from TB
    • %_IP Triggers (now disabled if not sharing a prescale)
      • xml change required – TMs are awaiting specifications
      • No triggers will change
ad