RC meeting and Run Plan, Saturday January 21st
Return to the RC Meeting Calendar
Contents
RC Meeting Information
Current RC: | Iuliia Skorodumina | |
Time: | Daily at 3:30PM | |
Location: | Counting House Conference Room |
Remote Connection Details
- Join ZoomGov Meeting
- https://jlab-org.zoomgov.com/j/1619032184?pwd=aWhTVWxya1ZZQzA1K2ZPSTd2ZX...
- Meeting ID: 161 903 2184
- Passcode: 260715
- Dial by your location
- +1 669 254 5252 US (San Jose)
- +1 646 828 7666 US (New York)
- +1 551 285 1373 US
- +1 669 216 1590 US (San Jose)
- 833 568 8864 US Toll-free
- Find your local number: https://jlab-org.zoomgov.com/u/acj3pTicMx
Summary
Friday Swing (01/20). Shift started in Controlled Access as the accelerator was still recovering from the repair and the HCal work was still ongoing in the hall. Around 6pm we requested beam permit and SBS on. MCC had troubles with turning the Corrector on, so we went back to Controlled Access and Jack Segal went down to the hall to unlock them. By 7:30pm we were in Beam Permit with all the magnets ON and waiting for the beam.
The accelerator recovery took longer than expected, so there was no beam until the end of Swing Shift. Swing Shift Summary (https://logbooks.jlab.org/entry/4113894).
Saturday Owl (01/21). At around 2am MCC started sending us CW beam and we started the beam recovery. First harp scans were not very good, but with the optics adjustments from MCC soon we get a good beam spot on target (0.46 and 0.48, which is within our new specifications, see https://logbooks.jlab.org/entry/4114126). We proceeded with the Carbon Hole run and checked the raster. The raster looked ok, so around 5am we went to production. Then we had a few complications.
First, there was a DAQ issue (https://logbooks.jlab.org/entry/4114174 and https://logbooks.jlab.org/entry/4114187). Thanks to the detailed How-to instructions, the Shift Crew was able to solve the problem.
Then, we had a problem with the target control (https://logbooks.jlab.org/entry/4114223 and https://logbooks.jlab.org/entry/4114227). It turned out that iocha26 crashed (https://logbooks.jlab.org/entry/4114228). Thanks to the detailed instructions from Arun, we managed to reboot it (https://logbooks.jlab.org/entry/4114254 and https://logbooks.jlab.org/entry/4114256).
Despite the difficulties, we were able to run production overnight. We took a few runs at 20 uA and at 35 uA and then went up to 45 uA around 8am.
We have the following issues with the detectors:
-- Hodoscope issue reappeared (https://logbooks.jlab.org/entry/4114198 and https://logbooks.jlab.org/entry/4114201).
-- GEM Layer 2 efficiency is low, but this layer probably need the software alignment after yesterday's work in the hall (https://logbooks.jlab.org/entry/4114218).
-- some issue with the BBCal threshold readback (https://logbooks.jlab.org/entry/4114196).
Run plan
- Continue production on pol He3 cell at 45 uA.
Shift Schedule
Please consider signing up for shifts [1].