Difference between revisions of "Run Planning Meeting Notes, February 9 - February 15, 2023"

From GlueXWiki
Jump to: navigation, search
(→‎Issues)
(→‎Past 24 hours)
 
(116 intermediate revisions by the same user not shown)
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]
 +
= Wednesday February 15 =
  
 +
=== Past 24 hours ===
 +
* [https://logbooks.jlab.org/entry/4131388 HARP scan results]
 +
* No beam between 9am and 12am (beam came back at midnight)
 +
* CCAL transported to experimental hall
  
 +
=== Shift Reports ===
 +
* [https://logbooks.jlab.org/entry/4131531 0400-1000]
 +
* [https://logbooks.jlab.org/entry/4131283 2200-0400]
 +
* [https://logbooks.jlab.org/entry/4131075 1600-2200]
 +
* [https://logbooks.jlab.org/entry/4130950 1000-1600]
 +
* [https://logbooks.jlab.org/entry/4130746 0400-1000]
 +
 +
=== Reports ===
 +
* [https://logbooks.jlab.org/entry/4131000 Hall D survey] (Moser/RadCon)
 +
* [https://logbooks.jlab.org/entry/4130972 CDC HVB current vs HV for 250nA HV scan runs on 4.5E-4RL Al on 17 Jan 2023] (Naomi)
 +
* gluon100 rebooted PS/PSC scalers are visible (Sergey)
 +
** Sasha also power cycled PS/PSC crates
 +
* Statistics balance
 +
**PARA 0/90: 20.7%
 +
**PERP 0/90: 20.2%
 +
**PARA 45/135: 21.1%
 +
**PERP 45/135: 19.7%
 +
**AMO : 18.3%
 +
 +
=== Issues ===
 +
* [https://logbooks.jlab.org/entry/4131558 TAGM discriminator TRG scaler gone wild]
 +
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.
 +
* BCM calibration. Alexandre recommends that we request a recalibration of AD00C BCM.
 +
 +
=== 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)
 +
 +
= Tuesday February 14 =
 +
 +
=== Past 24 hours ===
 +
* No beam between 6:50 am and 3pm
 +
* No beam between 4 pm and 9:50 pm
 +
* Cosmic run, # 120693, in raw mode at Beni request
 +
* [https://logbooks.jlab.org/entry/4130826 Around midnight lost PS & PSC rates on GlueX overview & MyaViewer][https://logbooks.jlab.org/entry/4130822](Sergey)
 +
 +
=== Shift Reports ===
 +
* [https://logbooks.jlab.org/entry/4130746 0400-1000]
 +
* [https://logbooks.jlab.org/entry/4130573 2200-0400]
 +
* [https://logbooks.jlab.org/entry/4130445 1600-2200]
 +
* [https://logbooks.jlab.org/entry/4130256 1000-1600]
 +
* [https://logbooks.jlab.org/entry/4130118 0400-1000]
 +
 +
=== Reports ===
 +
* [https://logbooks.jlab.org/entry/4130265 FCAL base status] (Mark)
 +
* Statistics balance
 +
**PARA 0/90: 20.5%
 +
**PERP 0/90: 20%
 +
**PARA 45/135: 20.8%
 +
**PERP 45/135: 20.1%
 +
**AMO : 18.6%
 +
 +
=== Issues ===
 +
* [https://logbooks.jlab.org/entry/4130573 Lost PS & PSC rates on GlueX overview & MyaViewer] (Amy/Sasha/Sergey)
 +
** gluon100 unaccessible (died)
 +
** gluon101 was used to restart the client but unsuccessfully
 +
* HARP taken due to miscommunication between RC & shift crew
 +
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.
 +
* BCM calibration. Alexandre recommends that we request a recalibration of AD00C BCM.
 +
 +
=== Plans ===
 +
* No maintenance day on Wednesday
 +
* 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 13 =
 +
 +
=== Past 24 hours ===
 +
* No beam since 6:50 am
 +
* Smooth data production whenever the beam is available
 +
* DAQ issue, lost 1hr
 +
 +
=== Shift Reports ===
 +
* [https://logbooks.jlab.org/entry/4130118 0400-1000]
 +
* [https://logbooks.jlab.org/entry/4129973 2200-0400]
 +
* [https://logbooks.jlab.org/entry/4129808 1600-2200]
 +
* [https://logbooks.jlab.org/entry/4129617 1000-1600]
 +
* [https://logbooks.jlab.org/entry/4129453 0400-1000]
 +
 +
=== Reports ===
 +
* Statistics balance
 +
**PARA 0/90: 20.5%
 +
**PERP 0/90: 20%
 +
**PARA 45/135: 20.8%
 +
**PERP 45/135: 20.1%
 +
**AMO : 18.6%
 +
 +
=== Issues ===
 +
* [https://logbooks.jlab.org/entry/4129931 DIRC LED issue] (Gabriel/Justin)
 +
* Rootspy crashes upon any interaction. See https://logbooks.jlab.org/entry/4129684
 +
* DAQ crashed, zero events recorded and could not restart (Amy/Sergey)
 +
* 6 FCAL base lockup in 72hrs
 +
* RC phone has no charger
 +
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.
 +
* BCM calibration. Alexandre recommends that we request a recalibration of AD00C BCM.
 +
 +
=== Plans ===
 +
* No bean during the day Wednesday (optics 4th pass RF sep) & Friday (debug beam current limitation for A &  C)
 +
* 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)
 +
 +
= Sunday February 12 =
 +
 +
=== Past 24 hours ===
 +
* Smooth data production whenever the beam is available
 +
* Unstable beam, low efficiency (BLM issue not RF)
 +
** [https://logbooks.jlab.org/entry/4129589 Machine degrading over time]
 +
 +
=== Shift Reports ===
 +
* [https://logbooks.jlab.org/entry/4129453 0400-1000]
 +
* [https://logbooks.jlab.org/entry/4129277 2200-0400]
 +
* [https://logbooks.jlab.org/entry/4129135 1600-2200]
 +
* [https://logbooks.jlab.org/entry/4128904 1000-1600]
 +
* [https://logbooks.jlab.org/entry/4128659 0400-1000]
 +
 +
=== Reports ===
 +
* Statistics balance
 +
**PARA 0/90: 19.8%
 +
**PERP 0/90: 20.9%
 +
**PARA 45/135: 20.9%
 +
**PERP 45/135: 19%
 +
**AMO : 20.4%
 +
 +
=== Issues ===
 +
* Upper computer monitor on console 4 shuts off and restarts spontaneously. Everything seems fine now, but this may be something to investigate when time allows. Not worth waking anyone up for. (Amy)
 +
 +
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.
 +
* BCM calibration. Alexandre recommends that we request a recalibration of AD00C BCM.
 +
 +
=== Plans ===
 +
* Expected downtime for part or the entire day shift
 +
* 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 11 =
 +
 +
=== Past 24 hours ===
 +
* Smooth data production
 +
* Entry to tagger (reboot TAGH HV frame & restore one missing channel) & experimental halls (move test setup)
 +
* No beam in the morning but Beam came back around noon
 +
* [https://logbooks.jlab.org/entry/4128221 HARP scans]
 +
** [https://logbooks.jlab.org/entry/4128200 Scan result for HALO:T:electron:tag:left:scaler_r1_vs_ hd:radiator:motor.RBV]
 +
** [https://logbooks.jlab.org/entry/4128204 HarpFitter: IHA5C11]
 +
** [https://logbooks.jlab.org/entry/4128205 HarpFitter: IHA5C11B]
 +
 +
=== Shift Reports ===
 +
 +
* [https://logbooks.jlab.org/entry/4128659 0400-1000]
 +
* [https://logbooks.jlab.org/entry/4128484 2200-0400]
 +
* [https://logbooks.jlab.org/entry/4128306 1600-2200]
 +
* [https://logbooks.jlab.org/entry/4128049 1000-1600]
 +
* [https://logbooks.jlab.org/entry/4127893 0400-1000]
 +
 +
=== Reports ===
 +
 +
* Statistics balance
 +
**PARA 0/90: 19.4%
 +
**PERP 0/90: 20.5%
 +
**PARA 45/135: 20.6%
 +
**PERP 45/135: 19.1%
 +
**AMO : 20.4%
 +
 +
=== Issues ===
 +
* FCAL bases lockup
 +
* Lost communication with TAGH HV frame => access tagger hall
 +
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.
 +
* BCM calibration. Alexandre recommends that we request a recalibration of AD00C BCM.
 +
 +
=== 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 10 =
 +
=== Past 24 hours ===
 +
* Data production resumed at 8:30 pm
 +
* High-Intensity Test (Naomi/Justin/Richard/Lubomir)
 +
** [https://logbooks.jlab.org/entry/4127288 Detector settings]
 +
** [https://logbooks.jlab.org/entry/4127311 AC position for low gain][https://logbooks.jlab.org/entry/4127275]
 +
 +
=== Shift Reports ===
 +
* [https://logbooks.jlab.org/entry/4127893 0400-1000]
 +
* [https://logbooks.jlab.org/entry/4127698 2200-0400]
 +
* [https://logbooks.jlab.org/entry/4127521 1600-2200]
 +
* [https://logbooks.jlab.org/entry/4127289 1000-1600]
 +
* [https://logbooks.jlab.org/entry/4127127 0400-1000]
 +
 +
=== Reports ===
 +
 +
* Statistics balance
 +
**PARA 0/90: 19.6%
 +
**PERP 0/90: 20.8%
 +
**PARA 45/135: 20%
 +
**PERP 45/135: 19%
 +
**AMO : 20.6%
 +
 +
=== Issues ===
 +
* 7 FCAL bases lockups
 +
* DAQ "crashed"
 +
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.
 +
* BCM calibration. Alexandre recommends that we request a recalibration of AD00C BCM.
 +
 +
=== Plans ===
 +
* No beam for most of the day due to beam study (high intensity instability for Hall A & B)
 +
* 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)
 +
* RF day (no beam for 8hrs) Wednesday or Thursday
  
−
= Wednesday February 9 =
+
= Thursday February 9 =
  
 
=== Past 24 hours ===
 
=== Past 24 hours ===
Line 24: Line 269:
  
 
=== Shift Reports ===
 
=== Shift Reports ===
−
* [0400-1000]
+
* [https://logbooks.jlab.org/entry/4127127 0400-1000]
 
* [https://logbooks.jlab.org/entry/4126946 2200-0400]
 
* [https://logbooks.jlab.org/entry/4126946 2200-0400]
 
* [https://logbooks.jlab.org/entry/4126857 1600-2200]
 
* [https://logbooks.jlab.org/entry/4126857 1600-2200]
Line 33: Line 278:
  
 
* Statistics balance  
 
* Statistics balance  
−
**PARA 0/90: 19%
+
**PARA 0/90: 20%
−
**PERP 0/90: 19%
+
**PERP 0/90: 18.9%
−
**PARA 45/135: 21%
+
**PARA 45/135: 19.9%
−
**PERP 45/135: 18%
+
**PERP 45/135: 19.8%
−
**AMO : 24%
+
**AMO : 21.4%
  
 
=== Issues ===
 
=== Issues ===
 +
* [https://logbooks.jlab.org/entry/4126964 Pressure readings] (Naomi)
 +
* [https://logbooks.jlab.org/entry/4127200 Beam energy variations from HALLD:p and HDTGR:p are anticorrelated ] (Alex. D)
 +
* Timing calibration [https://logbooks.jlab.org/entry/4127125][https://logbooks.jlab.org/entry/4127128] (Annika)
 
* Move the collimator while the beam is on
 
* Move the collimator while the beam is on
−
* [https://logbooks.jlab.org/entry/4126860 Bleedthrough (Alex D.)]
+
* [https://logbooks.jlab.org/entry/4126860 Bleedthrough] (Alex D.)
 
Pending:
 
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/4117764 Start Counter (Beni)] - We do not understand why there is a mismatch in the software between start counter and tracking.
Line 47: Line 295:
  
 
=== Plans ===
 
=== Plans ===
 +
* Accelerator, at the 9 am troubleshooting meeting will decide the course for today
 +
** Work on Optics either in Hall A arc (does not affect us) or machine (affect us => no beam) 
 +
* High-Intensity Test
 +
** Collect 100M events in production (sparsified) mode for beam currents of 900, 750, 600, 450, and 300 nA. 
 +
** Start with 900 nA to set the HV for the drift chambers, use Richard’s tool to set the TAGM thresholds and turn off the TOF and TAGH channels where the rates are too high
 +
** Take a run at each current setting with these conditions, followed by a few runs at 300 nA with matching HV settings for comparisons. 
 +
** Richard also requested that we take a small amount of mode 10 (unsparsified) data at the high currents as well, which should take a few minutes for each setting.
 
* Production (300 nA, 2h runs) with cycle:
 
* Production (300 nA, 2h runs) with cycle:
 
**2 runs PARA (0/90)
 
**2 runs PARA (0/90)

Latest revision as of 11:23, 15 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

Wednesday February 15

Past 24 hours

  • HARP scan results
  • No beam between 9am and 12am (beam came back at midnight)
  • CCAL transported to experimental hall

Shift Reports

Reports

Issues

Pending:

  • 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.

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)

Tuesday February 14

Past 24 hours

Shift Reports

Reports

  • FCAL base status (Mark)
  • Statistics balance
    • PARA 0/90: 20.5%
    • PERP 0/90: 20%
    • PARA 45/135: 20.8%
    • PERP 45/135: 20.1%
    • AMO : 18.6%

Issues

Pending:

  • 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.

Plans

  • No maintenance day on Wednesday
  • 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 13

Past 24 hours

  • No beam since 6:50 am
  • Smooth data production whenever the beam is available
  • DAQ issue, lost 1hr

Shift Reports

Reports

  • Statistics balance
    • PARA 0/90: 20.5%
    • PERP 0/90: 20%
    • PARA 45/135: 20.8%
    • PERP 45/135: 20.1%
    • AMO : 18.6%

Issues

Pending:

  • 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.

Plans

  • No bean during the day Wednesday (optics 4th pass RF sep) & Friday (debug beam current limitation for A & C)
  • 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)

Sunday February 12

Past 24 hours

Shift Reports

Reports

  • Statistics balance
    • PARA 0/90: 19.8%
    • PERP 0/90: 20.9%
    • PARA 45/135: 20.9%
    • PERP 45/135: 19%
    • AMO : 20.4%

Issues

  • Upper computer monitor on console 4 shuts off and restarts spontaneously. Everything seems fine now, but this may be something to investigate when time allows. Not worth waking anyone up for. (Amy)

Pending:

  • 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.

Plans

  • Expected downtime for part or the entire day shift
  • 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 11

Past 24 hours

Shift Reports

Reports

  • Statistics balance
    • PARA 0/90: 19.4%
    • PERP 0/90: 20.5%
    • PARA 45/135: 20.6%
    • PERP 45/135: 19.1%
    • AMO : 20.4%

Issues

  • FCAL bases lockup
  • Lost communication with TAGH HV frame => access tagger hall

Pending:

  • 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.

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 10

Past 24 hours

Shift Reports

Reports

  • Statistics balance
    • PARA 0/90: 19.6%
    • PERP 0/90: 20.8%
    • PARA 45/135: 20%
    • PERP 45/135: 19%
    • AMO : 20.6%

Issues

  • 7 FCAL bases lockups
  • DAQ "crashed"

Pending:

  • 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.

Plans

  • No beam for most of the day due to beam study (high intensity instability for Hall A & B)
  • 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)
  • RF day (no beam for 8hrs) Wednesday or Thursday

Thursday February 9

Past 24 hours

Shift Reports

Reports

  • Statistics balance
    • PARA 0/90: 20%
    • PERP 0/90: 18.9%
    • PARA 45/135: 19.9%
    • PERP 45/135: 19.8%
    • AMO : 21.4%

Issues

Pending:

  • 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.

Plans

  • Accelerator, at the 9 am troubleshooting meeting will decide the course for today
    • Work on Optics either in Hall A arc (does not affect us) or machine (affect us => no beam)
  • High-Intensity Test
    • Collect 100M events in production (sparsified) mode for beam currents of 900, 750, 600, 450, and 300 nA.
    • Start with 900 nA to set the HV for the drift chambers, use Richard’s tool to set the TAGM thresholds and turn off the TOF and TAGH channels where the rates are too high
    • Take a run at each current setting with these conditions, followed by a few runs at 300 nA with matching HV settings for comparisons.
    • Richard also requested that we take a small amount of mode 10 (unsparsified) data at the high currents as well, which should take a few minutes for each setting.
  • 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://halldweb1.jlab.org/wiki/index.php?title=Run_Planning_Meeting_Notes,_February_9_-_February_15,_2023&oldid=119124"