Difference between revisions of "Run Planning Meeting Notes, March 1 - March 8, 2023"
From GlueXWiki
(→Thursday March 2) |
(→Reports) |
||
Line 31: | Line 31: | ||
*[https://logbooks.jlab.org/entry/4141578 CDC AI HV control enabled] (David L) | *[https://logbooks.jlab.org/entry/4141578 CDC AI HV control enabled] (David L) | ||
*[https://logbooks.jlab.org/entry/4141642 Beam time structure](Hovanes) | *[https://logbooks.jlab.org/entry/4141642 Beam time structure](Hovanes) | ||
− | *[https://logbooks.jlab.org/entry/4141888 | + | *[https://logbooks.jlab.org/entry/4141888 Tagger Magnet efficiency checks] (Justin) |
*[https://logbooks.jlab.org/entry/4141704 Special TAGM Row 4 Runs] (Richard) | *[https://logbooks.jlab.org/entry/4141704 Special TAGM Row 4 Runs] (Richard) | ||
Revision as of 09:38, 2 March 2023
Zoom connect Meeting ID: 160 199 0060 / Passcode 8394
Hall D counting room white board
Thursday March 2
Past 24 hours
- MCC "Maintenance Day"
- TAGM work on radiated crates
- Production runs
- After separate ACC issue beam came back 22:05 or so. Thought we were not reaching Richard so I gave him a call at 22:30 just to make sure. Call is successful and Richard goes ahead and does studies on the TagM gains
Shift Reports
Reports
- second atmospheric pressure sensor added (Hovanes)
- 5x5 Sciglass Detector Prototype (Sasha)
- rho yields addressing TagM Issue (Alex)
- FDC wire discrepancy update (Lubomir)
- CDC AI HV control enabled (David L)
- Beam time structure(Hovanes)
- Tagger Magnet efficiency checks (Justin)
- Special TAGM Row 4 Runs (Richard)
Issues
- Coherent peak
- TAGM tripped off (MCC - Daniel)
- RF TDC
- MCC reports some phase shifts for beam @ 5th pass (all halls)
Plans
- Production (300 nA, 2h runs) with cycle:
- 2 runs PARA (0/90)
- 2 runs PERP (0/90)
- 2 runs PARA (45/135)
- 2 runs PERP (45/135)
- 1 run AMO (use it to rejuvenate AMO reference in CBREM EPICS GUI)
- Sasha left segments of detector prototype for RadCon survey on Survey Table. He looks to ask the likes of Scot for guidance as RadCon will have to come when beam is down for a sustained period time.
- Will we need a harp scan? MCC took away beam quite a while yesterday (nearly 14 hours before we got beam back)