Difference between revisions of "Run Planning Meeting Notes, February 23 - February 28, 2023"
From GlueXWiki
(→Issues) |
|||
| (5 intermediate revisions by the same user not shown) | |||
| Line 14: | Line 14: | ||
=== Past 24 hours === | === Past 24 hours === | ||
* Production runs | * Production runs | ||
| + | * TAGM row-by-row scan | ||
=== Shift Reports === | === Shift Reports === | ||
| Line 19: | Line 20: | ||
[https://logbooks.jlab.org/entry/4140782 Day] | [https://logbooks.jlab.org/entry/4140782 Day] | ||
[https://logbooks.jlab.org/entry/4140934 Swing] | [https://logbooks.jlab.org/entry/4140934 Swing] | ||
| + | [https://logbooks.jlab.org/entry/4140988 Owl] | ||
| + | |||
| + | === Reports === | ||
| + | *[https://logbooks.jlab.org/entry/4140983 CCAL check] (Sasha) | ||
=== Issues === | === Issues === | ||
*[https://logbooks.jlab.org/entry/4140883 diagnosing problems in the TAGM readout] (Richard) | *[https://logbooks.jlab.org/entry/4140883 diagnosing problems in the TAGM readout] (Richard) | ||
** [https://logbooks.jlab.org/entry/4140969 TAGM row-by-row scan] (Richard) | ** [https://logbooks.jlab.org/entry/4140969 TAGM row-by-row scan] (Richard) | ||
| + | ** [https://logbooks.jlab.org/entry/4140991 TAGM scalers using only row 4] | ||
| + | ** [https://logbooks.jlab.org/entry/4141000 turning off Vbias on rows 1-3 in TAGM] (Richard) | ||
| + | ** [https://logbooks.jlab.org/entry/4141052 Coherent peak after TAGM Vbias change] | ||
| + | |||
| + | === 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) | ||
| + | |||
| + | |||
= Tuesday February 28 = | = Tuesday February 28 = | ||
Latest revision as of 07:50, 1 March 2023
Zoom connect Meeting ID: 160 199 0060 / Passcode 8394
Hall D counting room white board
Contents
Wednesday March 1
Past 24 hours
- Production runs
- TAGM row-by-row scan
Shift Reports
Reports
- CCAL check (Sasha)
Issues
- diagnosing problems in the TAGM readout (Richard)
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)
Tuesday February 28
Past 24 hours
- Production runs
- Down during day shift due to SL dropping to restricted access twice
Shift Reports
Reports
Issues
- A couple of instances of the DAQ not stopping properly, requiring a reset/restart of the DAQ, after shift crew responding to DIRC tile alarms.
- Some runs missing from rcdb, corresponding in time to extended down time
- FDCHit Wiretime- hot channel
- Higher than normal TAGM baseline level (Beni)
- Hot pixels in DIRC, Update (Justin)
- FCAL reset left base off briefly (Mark D.)
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)
Monday February 27
Past 24 hours
- Production runs
Shift Reports
Issues
- There were multiple FCAL base lockups
- More on TAGM distribution
- Tagger NMR probe not working again (Hovanes)
Sunday February 26
Past 24 hours
- Production runs
Shift Reports
Reports
- After coming back from the downtime due to the Hall-D dipole trip, the diamond needed to be realigned (thanks Hovanes for coming in to take care of this)
- Initial checkout of newly installed CCAL (Sasha)
Issues
- CDC HV AI needed to be disabled
- Ratty TAGM distribution
- Same pending issues as before...
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)
Saturday February 25
Past 24 hours
- Beam came back at about 5:40 am Saturday morning after long downtime due to Hall-D dipole over-temperature trip.
Shift Reports
Reports
Issues
- Same pending issues as before...
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)
Friday February 24
Past 24 hours
Shift Reports
Reports
- Two FCAL bases replaced (Mark D.)
- First look at 2023 beam polarization from rho decays (Alex A.)
Issues
- Pending:
- Start Counter (Beni) - We do not understand why there is a mismatch in the software between start counter and tracking.
- TAGH hot channels w/ no beam
- Noise in FDC2 (Lubomir)
- FCAL11 crate problems (Sergey)
Plans
- Completion of CCAL installation
- 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)
Thursday February 23
Past 24 hours
- Production runs
- Cosmic run in raw mode when beam was down: Run 120800
Shift Reports
Reports
- New prototype in PS test stand: [1] (Sasha)
- CCAL ready for installation: [2] (Sasha)
- Accumulated statistics
Issues
- gluon04 spontaneously rebooted itself... which killed process providing main trigger rate to epics.
- DIRC LED Pulsers different from reference? -- midway through run.
- TAGM waveforms (Beni)
- Quality of coherent peak? Compare [3] from 2/15 and [4] from 2/22 and another for 45/135 perp: [5]
- Pending:
- Start Counter (Beni) - We do not understand why there is a mismatch in the software between start counter and tracking.
- TAGH hot channels w/ no beam
- Noise in FDC2 (Lubomir)
- FCAL11 crate problems (Sergey)
Plans
- Completion of CCAL installation: possible during MCC work in NL tomorrow morning ~8:30 for about an hour.
- 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)
