Difference between revisions of "Run Planning Meeting Notes, February 16 - February 22, 2023"

From GlueXWiki
Jump to: navigation, search
(→‎Issues)
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 17 =
 +
 +
=== Past 24 hours ===
 +
* Mark D. replaced the bad BCAL HV board with a new one at XX:XX.
 +
 +
=== Shift Reports ===
 +
* [https://logbooks.jlab.org/entry/4132353 0400-1000]
 +
* [https://logbooks.jlab.org/entry/4132224 2200-0400]
 +
* [https://logbooks.jlab.org/entry/4131994 1600-2200]
 +
* [https://logbooks.jlab.org/entry/4131761 1000-1600]
 +
* [https://logbooks.jlab.org/entry/4131531 0400-1000]
 +
 +
=== Reports ===
 +
[https://logbooks.jlab.org/entry/4102104 Please don't prestart very early] (Naomi)
 +
* Statistics balance
 +
**PARA 0/90: 20.9%
 +
**PERP 0/90: 19.9%
 +
**PARA 45/135: 20.8%
 +
**PERP 45/135: 20.4%
 +
**AMO : 18.1%
 +
 +
=== Issues ===
 +
* [https://logbooks.jlab.org/entry/4132216 A bad voltage board in the BCAL. Needs to be changed.] (Mark)
 +
* [https://logbooks.jlab.org/entry/4132129 HallD Run #120726: LED ADC reference SiPM time anomaly]
 +
Pending:
 +
* [https://logbooks.jlab.org/entry/4131558 TAGM discriminator TRG scaler gone wild]
 +
* [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.
 +
* BCM calibration. Alexandre recommends that we request a recalibration of AD00C BCM. (~30 mins?)
 +
 +
=== Plans ===
 +
* Install CCAL whenever there is an extended accelerator downtime
 +
** Restricted Access is needed to be able to use the ramp <-done
 +
** Cabling
 +
** Survey is needed
 +
* 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 16 =
 
= Thursday February 16 =
  

Revision as of 10:14, 16 February 2023

Zoom connect Meeting ID: 160 199 0060 / Passcode 8394

MCC whiteboard

Hall D counting room white board

Spreadsheet with list of runs

Integrated Trigger Count

Friday February 17

Past 24 hours

  • Mark D. replaced the bad BCAL HV board with a new one at XX:XX.

Shift Reports

Reports

Please don't prestart very early (Naomi)

  • Statistics balance
    • PARA 0/90: 20.9%
    • PERP 0/90: 19.9%
    • PARA 45/135: 20.8%
    • PERP 45/135: 20.4%
    • AMO : 18.1%

Issues

Pending:

Plans

  • Install CCAL whenever there is an extended accelerator downtime
    • Restricted Access is needed to be able to use the ramp <-done
    • Cabling
    • Survey is needed
  • 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 16

Past 24 hours

  • Production runs with a stable beam.
  • 2 BCAL HVs have been off since midnight due to a bad voltage board.

Shift Reports

Reports

Issues

Pending:

Plans

  • A bad BCAL HV board should be changed. Chris Stanislav is out today, and Mark D. is trying to find someone to change the BCAL board.
  • Install CCAL whenever there is an extended accelerator downtime
    • Restricted Access is needed to be able to use the ramp <-done
    • Cabling
    • Survey is needed
  • 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)
Retrieved from "https://halldweb.jlab.org/wiki/index.php?title=Run_Planning_Meeting_Notes,_February_16_-_February_22,_2023&oldid=119160"