My Field Manager Notes

Bookmarks ECALRunSequence ECAL P5 OnlineWBContactList EcalRFM PFG analyses

Trigger rates

Status

  • Must improve recovery procedure

  • FEDs in global:
    • ECAL: all!
      • trigger: all barrel
    • ES: only 548,549,551,553,554,555,556,557,560,561

  • Plans for Thursday:
    • Tests:
      • DCCs in EB+15 and EB+17
      • Endcap Selective Readout
      • DCC weights
      • SRP sTTS?
    • Local runs:
      • Gain Ratios
      • Pedestal Offset scan in EB+7
    • HV problems in EB+15 and EB+10

  • ZS thresholds with old weights
    • EB, ZS mode: L1ZS=L2ZS=7
    • EE, ZS mode: L1ZS=L2ZS=12
    • EB, SR mode: L1ZS=L2ZS=9
    • EE, SR mode: L1ZS=L2ZS=13

  • New weights (-383, -383, -372, 279, 479, 380)
    • EB, ZS mode: L1ZS=L2ZS=7
    • EE, ZS mode: L1ZS=L2ZS=12
    • EB, SR mode: L1ZS=L2ZS=8
    • EE, SR mode: L1ZS=L2ZS=13

9 Aug 2009

  • Smooth except for "LED accident"

8 Aug 2009

  • Magnet ramped up at 14
  • Pedestal offset scan taken
  • Back to global at ~18.00

7 Aug 2009

  • Magnet rump-up Sat not before 9am
  • Technical stop 17 Aug will be postponed

5 Aug 2009

  • Running smoothly overnight. SR in EB since yesterday
  • Few spikes in the EG1 L1 rate.
    • Being investigated and seems related to individual crystals/trigger towers.
    • Has periodicity
  • Three FEDs out of the run. Will stay like this.
  • HLT excercise: EB- and EE+ (test SR)

4 Aug 2009

11h Run Meeting
  • Magnet up again in Friday. Rumping up at 12.
  • No changes to infrastructure until Friday
    • Pump delayed
    • No intervention in the cavern
  • Thursday technical shift confirmed

  • DAQ would like to take ECAL runs to debug the HLT
    • missing HCAL events
    • commission EG paths

  • Data ops
    • 3_2_3 being deployed. Will be used from next run on.

3 Aug 2009

  • Running smoothly during the night.
  • Observed few spikes in the trigger.
  • Took ~2.5 hours to recover crystals after power cut
    • ~1hour to turn on and check DCS (all crates were switched off by hand)
    • ~1.5hour for DAQ (mostly because of one FED)
  • ES was faster ~1hour
  • Ready for global at ~22.15. First run at 1am!
  • Very severe noise seen at 2am
  • Running in Selective Readout with EB-. Waiting for T0 to be ready.

2 Aug 2009

  • Cooling problem caused ES and laser to go off at ~20.00
  • ES eventually recovered at 1am

1 Aug 2009

  • Running without Laser from 6 in the morning. Laser eventually rapaired during the morning. At 11 still waiting for the run finish.
  • Discovered that we are triggering on test pulse.

31 Jul 2009

  • Problem with DCC weights in EE- and EB+ after yesterday excercise. Fixed by power-cycling crates.
  • One more laser problem in the morning

30 Jul 2009

  • Summary of the day:
    • FEDs with problems last night go recovered
      • 632 (EB+5) spontaneously
      • 613 () power-cycling the crate
    • FEDs with problem from last week
      • EE+4, EB+15, EB+17 have missing SRP block, but SRP decision applied. Firmware issue, could explain last week instabilities.
      • nevertheless running in ZS and SR mode (not destroying anything)
    • Took validation runs with SR and ZS at 100 (!) and 30 kHz respectively
    • DCC zero suppression weights still have tecnical problems. Can not reliably check whether the values were correctly configured
    • SRP problems fixed * out-of-sync caused by wrong masking + timeout failure in the firmware: fixed by fixing the software
    • Trigger key coming

  • ES program for the day
    • firmware burning to eprom
    • check that local running does not interfere with global
    • look at pedestals w/ magnetic field
    • common mode algo test @1kHz

29 Jul 2009

11h Run Meeting
  • "No change" means "no change"
  • News on the magnet
    • if we are close to the goal of 300M triggers by the end of 1st week of August, the magnet uptime might be extended
    • then we might go to a second phase were we focus more on understanding the system w/ magnetic field
  • Last 13h 1h down-time

  • Very high trigger rate during the night. ECAL taken out of the trigger for the night.
    • Understood to be a mistake of the trigger shifter that put EE in.
    • Situation restored in the morning.

  • ES event mismatch errors.

28 Jul 2009

  • Running smoothly during the night.

11h Run Meeting
  • No 2T run. Should be at 3.8T by 16. Start run by 18.00.

  • Afternoon
    • Switched on ECAL at ~15.45
      • Four supermodules had problems with HV. Eventually solved by power-cycling.
      • Laser air conditioning problem also eventually fixed.
    • Loaded and verified the 3.8T pedestal offsets
    • Joined the global run at ~17.00

27 Jul 2009

  • Saturday: problem in Laser barrak. No communication GPIB controller. Hard reset of the system solved the problem.

  • During the night: problem in Laser barrak. No communication GPIB controller. Expert intervention in the morning fixed the problem.

  • Saturday night: L1EG10 trigger rate went to 250Hz for 1.5hours and then dropped again to 100Hz. Being investigated by PFG. Nothing clearly anomalous seen.

  • ECAL off at 8.15-8.45. Expected to be off until the magnet reaches stable conditions.

11h Run Meeting

  • Manget rump-up
    • HF sudden movement at 1.6 was inelastic. 4mm towards the IP. Didn't go back a 0T.
    • Plan to go 100 A/s. Should be at 3.8 by the end of the day.
    • Problem yesterday with cooling. Principal circuit not working, when back-up was running out of He a slow discharge interlock was triggered. HCAL didn't manage to run. ECAL managed to by-pass the interlock.

  • Problem with magnet. Restart at 0T sometime in the afternoon.
Edit | Attach | Watch | Print version | History: r24 < r23 < r22 < r21 < r20 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r24 - 2009-08-11 - PasqualeMusella
 
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    Main All webs login

This site is powered by the TWiki collaboration platform Powered by PerlCopyright &© 2008-2024 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
or Ideas, requests, problems regarding TWiki? use Discourse or Send feedback