RC meeting and Run Plan, Tuesday, June 10th

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 (Since ~11:30 AM we are temporarily running 7 uA LH2 to better understand GEM noise/efficiency)

Run plan for Today

  • Production on LH2
    • PS10=0, PS16=9
    • Config: "GEp-5-3Stream-NoHcalScalers"
    • Thresholds: ECAL = 65%, HCAL = 20% (depending on rate limitation)
    • Four hours runs
    • 5k replay every 15 minutes
    • Monitor Scaler Rates
  • Run plan to understand GEM efficiency:
    • Do most of this plan GEM expert-driven during day/swing until completed.
    • How to run during owl? Default setting: return to 3650/85% and 15 uA (with corrections) until the data can be analyzed and until the special test runs are completed
    • We already have 2 hours of 7 uA data in the bank at current HV settings
    • Tuesday June 10, swing: repeat the conditions of runs 4383-4385 at 7 uA for 2 hours each.
    • Time permitting: go back to 3650/85% setting and run there at 7 uA for 2 h
    • Wednesday day/swing:
      • Repeat the conditions of runs 4382-4385 at [15-18?] uA for one hour each.
      • Take a run with 3650/85% with corrections at [15-18] uA (one hour).
      • Take a run with 3625/85% with corrections at [15-18] uA (one hour).
    • Analyze data. Experts will decide modifications to this plan.
  • GEM run plan from GEM team
    • Begin with 7 uA data, 2 hr runs (Tuesday Swing) COMPLETED
      • 3927 V @ 95% (current setting)
      • 3905 V @ 95%
      • 3881 V @ 95%
      • 3857 V @ 95%
      • 3650 V @ 85% (beginning of Kin3, end here, increase current to 15 uA and run overnight)
    • Move to 15-18 uA (live time dependent?) (Wednesday Swing)
      • 3650 @ 85% w/ corrections overnight
    • Higher current scans, 1hr runs w/ corrections (Thursday day)
      • 3927 V @ 95%
      • 3905 V @ 95%
      • 3881 V @ 95%
      • 3857 V @ 95%
      • 3625 V @ 85%
      • Return to 3650 V @ 85% + corrections, run here until data can be analyzed

Key Updates, Last 24 hours

  • Relatively smooth running at 15 uA.
  • A few hours were lost here and there to DAQ issues and accelerator downtimes
  • HCAL threshold lowered to 20% of elastic:
  • ECAL threshold increased to 65% of elastic:
  • kept running 15 uA overnight

Accumulated Charge

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

Current Issues

  • BTA is fixed log entry
  • 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
  • NEW June 10 morning: Concern over GEM HV settings. Tracking efficiency seems much lower in some of the replays completed after GEM HV increases that took place on or around 5/24. Data seem dominated by accidentals/false tracks, and no elastic peaks are visible. Initially there was some concern about the trigger timing due to ECAL delay adjustments made around the same time: log entry. However, on further investigation it became clear that the trigger timing was not the issue, and that the tracking analysis is dominated/overwhelmed by false tracks and noise. Elastic peaks still emerge in some runs in this range with a coincidence time cut centered around the (shifted) peak. But the number of successfully reconstructed events is much lower than in earlier runs taken at similar current. While there is some hope to eventually deal with this situation in software, we need to more systematically figure out what is a good operating HV for the GEMs.

Shifts

  • Next available: Saturday June 14 Swing SL

Subsystem Updates

  • ECal:

Not much new over past couple days. Time available tomorrow to check a few channels on scope? Whenever there's time, not urgent. Don has been trying to get replay working on the farm. Regular replay with no GEMs, to monitor ECAL and test pi0 calibration. Seems to be working

  • HCal:

Nothing new to report (other than threshold decrease).

  • GEMS:

Jacob: got a phone call last night. A sector in one back tracker module kept tripping off. Reduced HV overnight. This morning increased back to where it was and increased trip limit. If time available tomorrow, Ching-Him needs to remove an HV crate; would need Radcon survey. Not urgent.

  • CDET:
  • DAQ:

No, just got a call about HCAL scalers, rebooted crate and it was fine.

  • 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,_Tuesday,_June_10th&oldid=8527"