Run Planning Meeting Notes, Jan 30-Feb 05, 2020

From GlueXWiki
Revision as of 09:20, 4 February 2020 by Ostrov (Talk | contribs)

Jump to: navigation, search

Trigger Spreadsheet

Trigger Counter

Wednesday, February 5

  1. Last 24 hours
  2. Issues
  3. Reports
  4. Plans for today

Tuesday, February 4

  1. Last 24 hours
    • No beam: 11pm - 2:30am (beam tunning)
    • Bad beam: since 5am - unstable and shifted by 3mm at AC (5th path separator issues).
    • 9:30am: The latest harp scan [1]
    • About 3.2B production triggers.
  2. Changes
    • 2pm: Same AMO reference in RootSpy as in cohbream gui [2]
    • 4pm: A change in the data-taking procedure [3]:
      • MCC should insert a dumplette before each no-beam goniometer movement
      • Two production runs in a row for each radiator configuration.
  3. Issues
    • Display dumplette location on goniometer GUI
    • Problems with coherent peak at the start of the swing shift. [4],[5]
    • At 8pm, a number of IOC and DAQ stopped working for about 10 minutes. A network glitch is suspected. [6]
  4. Reports
    • Ratio of rates from HOSS [7]
    • More on ratio of rates [8]
    • Drifting beam energy [9]
  5. Plans for today
    • Production, production and more production.

Monday, February 3

  1. Last 72 hours
    • Friday:
      • No beam 10am-12pm (BLA calibration). Opportunistic Hall access.
      • No beam 3pm-4pm (MCC software update).
      • No beam 4pm-11pm (lost vacuum in Hall C transport [10]).
    • Saturday:
      • Goniometer stopped moving sometime between 5am and 3pm. The problem was only noticed at 3pm [11]. As a result, a few runs have unknown diamond orientation [12],[13]
      • Repair work on goniometer from 4pm till 7:30pm (no beam) [14]
      • At 10pm, lost HV on TAGH 121-127 and beam halo. HV crate T8-1-BOT has died and wouldn't boot. Repairs were postponed until next morning [15], [16]
    • Sunday:
      • Night shift took data with TAGH hole [17]
      • No beam 8:15am-9:15pm (ARC8 magnet overheating)
      • 9:30am-10:30am Controlled tagger access by Nick to repair T8-1-BOT [18]
      • Beni conducted ST counter SiPMT tests [19] and raised TOF HV.
      • Finally, beam came back at 9:15pm.
    • Production
      • In all the chaos over weekend, we managed to collect 7.9B triggers. However, 1.9B events have an unknown diamond orientation, and 1.7B tirggers have beam energy hole.
  2. Changes
    • Change in TPOL readout [20], [21]
    • New DIRC SiPM TDC reference timing [22] - apparently, it's still not in ccdb.
    • New TOF high voltages [23]
  3. Issues
    • TAGM is "immobilized" to keep goniometer moving.
    • TPOL slot 13 channel 3 is always saturated [24]
    • Remote reset cable for T8-1-BOT needs to be repaired.[25]
    • FDC HV channel 2:c4:4p was in constant trip loop and was set to lower HV [26], [27]
    • TOF T:45 20V difference between HV setpoint and readback.
    • Gluon05 needs to be rebooted almost daily.
    • As ususal, new DIRC holes require DAQ reboots.
    • Do we need a dumplette inserted for all goniometer movements? [28]
  4. Noteworthy
    • MCC sees our radiator IN & OUT at the same time [29]
  5. Reports
    • Ratio of rates [30]
    • Vertex plots for empty target [31]
  6. Plans for today
    • Harp scan
    • Production

Friday, January 31

  1. Last 24 hours
    • JD70-106 47um diamond alignment till 4pm [32], [33]
    • Ion chambers had to be masked for alignment [34], [35]
    • Production since 4pm (~3.5B triggers)
  2. Issues
    • JD70-105 keeps degrading [36]
    • Periodic holes in DIRC occupancy [37]. Any way to recover without full DAQ reboot?
    • "Disappeared" DIRC SiPM TDC [38] - its timing recalibration is not done yet
    • Oh yes, Great Battle of the Mouse for 3 hrs :) [39]
  3. Reports
    • More on initial PS enhancement [40]
  4. Plans for today
    • We may (or may not) have ~30min for access at 10am
    • Production

Thursday, January 30

  1. Last 24 hours
    • Harp scan (~9am) [41]
    • Alignment of JD70-106 47um diamond (9:30am till 6pm) [42]
    • Production at 350nA (since 6pm). About 2.6B triggers collected.
  2. Issues
    • DIRC N-board lost connectivity for 30 minutes [43]
    • Gamma radiation at the racks [44]
    • Uncoupling of DIRC and FCAL light censors [45],[46]
    • Online monitoring issues [47] and fixed calibrations [48], [49]
  3. Reports
    • Initial PS enhancement Spring 2020 [50]
  4. Plans for today
    • Any more work on diamond alignment?
    • Production
Retrieved from "https://halldweb.jlab.org/wiki/index.php?title=Run_Planning_Meeting_Notes,_Jan_30-Feb_05,_2020&oldid=96311"