RC meeting and Run Plan, Thursday, June 19th

From SBS wiki
Jump to: navigation, search

Back to the calendar

RC Meeting Information

Current RC: Silviu Covrig Dusa

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

Zoom info

Useful Links

Current Status

  • Production

Run plan for Today

Production on LH2

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

Key Updates, Last 24 hours

  • Beam back from beam studies around 12:50 yesterday, cross check, beam raster and positions checked fine, went to production
  • Machine was down for about 2h, during Swing, due to 2 cavities dropping out of HV (2L18 and 1L06, 2L18 was bypassed)
  • 8h run-plan with HCAL threshold at 10% and ECAL at 70%, beam current 15 µA completed Swing-Owl
  • GEM baseline studies during Swing, baseline adjusted from 400-500 ADC ch to 800-900 ADC ch, summary in https://logbook.jlab.org/entry/44090882
  • Since run 4770, 6:30am today, we are running at 22 µA beam current with HCAL at 20% and ECAL at 70% and new GEM baseline, the plan is to stay here until further notice

Accumulated Charge

  • Total Accumulated Charge at Kin3 so far: 25.82 C (Goal: 100 C)
  • Total Accumulated Charge at Kin3 since June 18 Swing: 0.9 C

Current Issues

  • Plagued by DAQ crashes, every shift seems to be at least an hour of wasted beam time due to DAQ crashes and recoveries
  • 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 :)

Subsystem Updates

  • ECal:
  • HCal:
  • GEMS:
  • CDET:
  • DAQ:
  • 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 @ 22 µ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,_Thursday,_June_19th&oldid=8581"