Difference between revisions of "Run Planning Meeting Notes, February 23 - February 28, 2023"
From GlueXWiki
(→Plans) |
|||
| Line 8: | Line 8: | ||
[https://halldweb.jlab.org/data_monitoring/run_statistics/RunPeriod-2023-01/index.html Integrated Trigger Count] | [https://halldweb.jlab.org/data_monitoring/run_statistics/RunPeriod-2023-01/index.html Integrated Trigger Count] | ||
| + | |||
| + | = Friday February 24 = | ||
| + | |||
| + | === Past 24 hours === | ||
| + | * Production runs | ||
| + | |||
| + | === Shift Reports === | ||
| + | [https://logbooks.jlab.org/entry/4137188 Early riser] | ||
| + | [https://logbooks.jlab.org/entry/4137394 Day] | ||
| + | |||
| + | === Reports === | ||
| + | |||
| + | [https://logbooks.jlab.org/entry/4137324 Two FCAL bases replaced] (Mark D.) | ||
| + | |||
| + | == Issues === | ||
| + | |||
| + | |||
| + | *Pending: | ||
| + | ** [https://logbooks.jlab.org/entry/4117764 Start Counter (Beni)] - We do not understand why there is a mismatch in the software between start counter and tracking. | ||
| + | ** [https://logbooks.jlab.org/entry/4133378 TAGH hot channels w/ no beam] | ||
| + | ** [https://logbooks.jlab.org/entry/4133666 Noise in FDC2] (Lubomir) | ||
| + | ** [https://logbooks.jlab.org/entry/4133998 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 = | = Thursday February 23 = | ||
Revision as of 14:25, 23 February 2023
Zoom connect Meeting ID: 160 199 0060 / Passcode 8394
Hall D counting room white board
Contents
Friday February 24
Past 24 hours
- Production runs
Shift Reports
Reports
Two FCAL bases replaced (Mark D.)
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)
