RC meeting and Run Plan, Sunday, June 15th

From SBS wiki
Jump to: navigation, search

Back to the calendar

RC Meeting Information

Current RC: Nathan Heinrich

RC Daily Meetings1:00 PM All Days, via Zoom and in person in the counting house meeting room (2nd floor).
No meeting planned for the weekend, Unless something important comes up

Zoom info

Useful Links

Current Status

  • Production running

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) COMPLETED
      • 3650 @ 85% w/ corrections overnight
    • Higher current scans, 1hr runs w/ corrections (Thursday day) COMPLETED
      • 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
      • 1 hour run with HV corrector script off to test effect of copper shielding

Key Updates, Last 24 hours

  • Overnight just had a few DAQ crashes but no serious issues
  • During Day shift today The coolant in the Target got low because a JT valve in Hall C got stuck open. This got fixed after about 1 hour, and we're back to running.

Accumulated Charge

  • Total Accumulated Charge at Kin3 so far: 22.7 C (Goal: 100 C)
  • Total Accumulated Charge at Kin3 since June 11 Swing: 2.6 C

Current Issues

  • Lower than optimal beam current due to GEM occupancy/efficiency/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 (~25,000 jobs). These replays are ~60% complete as of this writing. While it may still be inefficient, the hope is that these replays will at least give us enough elastic ep to iterate on ECAL and HCAL calibrations
  • Uncertaintly regarding GEM gain/HV settings. Tracking efficiency seemed much lower in some of the replays completed after GEM HV increases that took place on or around 5/24. Data seemed dominated by accidentals/false tracks, and no elastic peaks were clearly 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. On further analysis the situation for these runs seems less dire than initially feared. However, the GEM HV studies currently being carried out parasitically should nevertheless help improve our understanding when the data can be analyzed
  • Counting house access to /cache (gateway??) (Helpdesk ticket in)

Shifts

  • Full up for until August at the moment :)

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,_Sunday,_June_15th&oldid=8549"