RC meeting and Run Plan, Monday, June 9th

From SBS wiki
Jump to: navigation, search

Back to the calendar

RC Meeting Information

Current RC: Andrew Puckett

RC Daily Meetings1:00 PM All Days, via Zoom and in person in the counting house meeting room (2nd floor).

Zoom info

Useful Links

Current Status

  • Running production at 15 uA LH2
  • ongoing downtime (as of this writing): log entry

Run plan for Today

  • Production on LH2
    • PS10=0, PS16=9
    • Config: "GEp-5-3Stream-NoHcalScalers"
    • Thresholds: ECAL = 60%, HCAL = 20-25% (depending on rate limitation)
    • Four hours runs
    • 5k replay every 15 minutes
    • Monitor Scaler Rates


Key Updates from Friday

  • Relatively smooth running at 15 uA over the weekend.
  • A few hours were lost here and there to DAQ issues and accelerator downtimes
  • The VTP config files for GEM online common-mode calculations were updated to use a lower limit of zero on the first iteration of averaging: log entry. The motivation for this was the concern that the existing online CM algorithm leads to too-aggressive zero suppression at high GEM occupancies. After making this change for ALL APVs in front and back trackers, the overall data rate went down by about 12% since the APVs were reporting a common-mode out-of-range condition less often, but the raw, "online" occupancies actually went UP, from 40% to over 50% for the first six layers of the front tracker, and smaller changes (mostly increases) for the X/Y layers in both front and back trackers, suggesting the previous configuration was probably in fact too aggressive with ZS. The increased online occupancy may also be a symptom of large negative "signals" included in the first iteration of the common-mode averaging pulling down the baseline, causing the APVs to save a significant amount of baseline noise as "signal" (however, we already developed a machinery to measure and correct for this bias on an event-by-event basis using the full readout events for the GMN analysis). This issue increases the urgency to deploy region-of-interest readout for the GEMs and either disable ZS altogether in the front tracker or deploy the more robust "histogramming" algorithm.
  • Monday morning (HCAL trigger threshold concern): there is concern about the energy calibration of HCAL and the trigger efficiency; Kip is investigating the energy calibrations currently used for both online triggering and offline analysis against Kin. 1 data. In the meantime, we will attempt to run with a further reduced HCAL threshold of 20-25% of the elastic peak energy (if the DAQ can handle), until we are able to obtain an HCAL calibration we are more confident leads to an efficient trigger. log entry

Accumulated Charge

  • Total Accumulated Charge at Kin3 so far: 19.09 C (Goal: 100 C)
  • Total Accumulated Charge at Kin3 since June 4 Swing: 3.6 C

Current Issues

  • BTA still not working in the sense of ABU/BANU numbers properly loading from EPICs. Evidently some other halls are having problems with their BTA scripts as well. Experts are investigating.
  • Counting house access to /cache (gateway??) (Helpdesk ticket in)
  • Lower than optimal beam current due to GEM occupancy and signal/noise concerns.
  • APV baseline sagging/broadening: HV test showed a significant reduction of the width at lower gain. Need tracking analysis to check whether the proton efficiency is good at such a gain.
  • Online zero suppression performance (common-mode min values for online zero suppression were changed to zero for the first iteration of averaging until we are ready to deploy ROI readout and histogramming firmware).
  • HCAL calibration/trigger efficiency
  • Slow tracking/analysis difficulty/flying blind: Andrew made some updates to the tracking code over the weekend to try to improve the tracking efficiency/accuracy/speed. Started cooking about 8 C worth of kin. 3 production data (~25000 jobs). While it may still be inefficient, the hope is that these replays will give us enough elastic ep to iterate on ECAL and HCAL calibrations
  • Others?

Shifts

  • Next available: Saturday June 14 Swing SL

Subsystem Updates

  • ECal:

Jhih-Ying: Different issues over the weekend/easily taken care of. Friday evening: VXS crate 4 and 5 in VTP energy missing, rebooted crates and this fixed the issue. On owl shift Saturday, lost lower section of ECAL in ADC plots. VXS crate 1 reboot fixed. Saturday evening; lost communication to Rpi2 and 10--HV crate 2 and 10, reboot fixed. Everything good now. Heating system: Friday evening, a "blip" that corrected itself. Sunday: readout issue one card froze, rebooted this morning

  • HCal:

Nothing to report

  • GEMS:

Jacob: besides the change to CM min, there was a sector on last layer of back tracker that seemed to develop a short and then recovered. MyA plot not working at the moment but we'll get an update later. Strip hit distribution plots "grass", restarting run fixes.

  • CDET:

Running smooth in general. Ben: think we got ref signal working on the last maintenance day. 50k hits in 50k replay. ~40 ns jitter (?!) Window adjusted to center on timing peak and shrink window. Trailing edge at zero. Will start to subtract reference signal to improve time resolution.

  • DAQ:

People on shift mostly able to recover DAQ issues on their own.

  • Analysis:

Beam Restoration Procedure

Beam requirements

  • start off at 5 pass beam
  • intrinsic beam size (at target): 150–600 µm
  • raster size: 2 mm X 2 mm
  • During kin#3 SBS magnet will be at 1762.23 Amp, the corrector magnets at -80A for all.
  • production run @ 15 µA for now
  • For later
    • production beam current : 25-30 µA
Retrieved from "https://sbs.jlab.org/wiki/index.php?title=RC_meeting_and_Run_Plan,_Monday,_June_9th&oldid=8518"