Difference between revisions of "Run Planning Meeting Notes, October 26 - November 2, 2022"
From GlueXWiki
(→Issues) |
(→Thursday, October 27) |
||
| Line 11: | Line 11: | ||
=Thursday, October 27= | =Thursday, October 27= | ||
=== Past 24 hours === | === Past 24 hours === | ||
| − | * | + | * Smooth running with empty target |
| − | * CDC Pressure alarms | + | * 6 CDC Pressure alarms: new run started each time, last one required DAQ crate reboot (delayed restart) |
=== Shift Summary === | === Shift Summary === | ||
| Line 22: | Line 22: | ||
=== Issues/Reports === | === Issues/Reports === | ||
| − | * [https://logbooks.jlab.org/entry/4069731 32 ns shift in tagger crate] | + | * [https://logbooks.jlab.org/comment/41666#comment-41666 Avoid long prestarts] |
| + | * [https://logbooks.jlab.org/entry/4069731 32 ns shift in tagger crate] (no action required) | ||
* [https://logbooks.jlab.org/entry/4070799 SC Dark Current/Rates] (Beni) | * [https://logbooks.jlab.org/entry/4070799 SC Dark Current/Rates] (Beni) | ||
* Do we still want beam strip charts in the logbook every 2 hours (as noted on white board)? | * Do we still want beam strip charts in the logbook every 2 hours (as noted on white board)? | ||
=== Plan === | === Plan === | ||
| − | * RF recovery for 4 hours this morning, starting at 8 am: target testing, then | + | * RF recovery for 4 hours this morning, starting at 8 am: target testing, then |
** Expect to start beam recovery around noon | ** Expect to start beam recovery around noon | ||
| + | ** Fill target before beam returns for production data | ||
* Harp scan after beam is restored(?), more than a week since the last one (Alexandre) | * Harp scan after beam is restored(?), more than a week since the last one (Alexandre) | ||
Revision as of 08:40, 27 October 2022
Meetings are via ZoomGov: connect (Meeting ID: 160 199 0060 / Passcode 8394)
Hall D counting room white board
Back to Run Coordination Meetings:Fall2022
Thursday, October 27
Past 24 hours
- Smooth running with empty target
- 6 CDC Pressure alarms: new run started each time, last one required DAQ crate reboot (delayed restart)
Shift Summary
Issues/Reports
- Avoid long prestarts
- 32 ns shift in tagger crate (no action required)
- SC Dark Current/Rates (Beni)
- Do we still want beam strip charts in the logbook every 2 hours (as noted on white board)?
Plan
- RF recovery for 4 hours this morning, starting at 8 am: target testing, then
- Expect to start beam recovery around noon
- Fill target before beam returns for production data
- Harp scan after beam is restored(?), more than a week since the last one (Alexandre)
